Data as of Nov 5, 2026
77.128.0.0/13
No anonymizer spaceSociete Francaise Du Radiotelephone - SFR SA
Residential-proxy exits
Proxy exits
9,442
1.8% of its addresses · listed by providers
Always-on exits
275
2.9% of its exits
Spread
752 of 2,048
/24s with at least one exit
Providers
113
selling exits here
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 77.130.243.0/24 | 26 | 256 | |
| 77.133.250.0/24 | 19 | 256 | |
| 77.133.249.0/24 | 12 | 256 | |
| 77.131.12.0/24 | 11 | 246 | |
| 77.128.219.0/24 | 5 | 8 | |
| 77.130.172.0/24 | 3 | 9 | |
| 77.128.194.0/24 | 3 | 7 | |
| 77.130.88.0/24 | 3 | 6 | |
| 77.132.33.0/24 | 3 | 5 | |
| 77.132.175.0/24 | 3 | 4 | |
| 77.129.219.0/24 | 2 | 9 | |
| 77.130.191.0/24 | 2 | 9 | |
| 77.128.18.0/24 | 2 | 8 | |
| 77.133.40.0/24 | 2 | 8 | |
| 77.131.53.0/24 | 2 | 7 | |
| 77.132.87.0/24 | 2 | 7 | |
| 77.135.153.0/24 | 2 | 7 | |
| 77.128.252.0/24 | 2 | 6 | |
| 77.132.105.0/24 | 2 | 6 | |
| 77.128.57.0/24 | 2 | 5 | |
| 77.128.201.0/24 | 2 | 5 | |
| 77.133.0.0/24 | 2 | 4 | |
| 77.132.167.0/24 | 2 | 4 | |
| 77.129.22.0/24 | 2 | 4 |
Proxy providers listing exits
- 2Captcha
- 2Extract
- 711Proxy
- 9Proxy
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BirdProxies
- BlurPath
- BottingTools
- Bright Data
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- FuseProxy
- GSocks
- GeekProxy
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HideProxy
- HydraProxy
- IPCola
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- KocerRoxy
- Kookey
- LemonBright
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MagneticProxy
- MangoProxy
- MarsProxies
- Maskify
- MoMoProxy
- MrScraper
- NSocks
- NextProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PSBProxy
- PacketStream
- PrivateByte
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Cheap
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- RainProxy
- RapidProxy
- RealProxy
- ResiProxies
- RoamProxy
- RolaProxy
- Shifter
- Smartproxy
- SpyderProxy
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- TrueProxies
- TrustProxy
- VProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- Webshare
- YumiProxy
Announcements
More specific
Announcements inside
| Prefix | Origin | Type | Proxy exits | Holder | RPKI |
|---|---|---|---|---|---|
| 77.134.204.0/24 since Apr 2020 | AS15557 | Residential | 2 | Societe Francaise Du Radiotelephone - SFR SA via Fixed IP |
Registrations in this block
The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 77.128.0.0/11 | 2,097,152 | FR-SFR-20100831 | Societe Francaise Du Radiotelephone - SFR SA (ORG-VF1-RIPE) · FR | ALLOCATED PA | Aug 31, 2010 | abuse@ |
| └ 77. | 499,712 | SFR-USER-DATA | Fixed IP | SUB-ALLOCATED PA | Jan 21, 2020 | abuse@ via FR-SFR-20100831 |
| └ 77.128.0.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.1.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.2.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.4.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.8.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.16.0/20 | 4,096 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.32.0/20 | 4,096 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.48.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.52.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.53.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.54.0/23 | 512 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.56.0/22 | 1,024 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.60.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.61.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.62.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.64.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.72.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.76.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.78.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.79.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.80.0/20 | 4,096 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.96.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.104.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.106.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.107.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.108.0/22 | 1,024 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.112.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.114.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.115.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.116.0/22 | 1,024 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.120.0/21 | 2,048 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.128.0/20 | 4,096 | FR-NCNUMERICABLE | Dynamic pools | ASSIGNED PA | Oct 7, 2015 | abuse@ via SFR-USER-DATA |
| └ 77.128.144.0/20 | 4,096 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.128.160.0/19 | 8,192 | SFR-USER-DATA | B2B | SUB-ALLOCATED PA | Jul 3, 2026 | abuse@ via SFR-USER-DATA |
| └ 77.128.182.8/29 | 8 | MINISTERE_ | Service Business | ASSIGNED PA | Jul 3, 2026 | abuse@ via SFR-USER-DATA |
| └ 77.128.192.0/18 | 16,384 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.0.0/19 | 8,192 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.32.0/20 | 4,096 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.48.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.52.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.53.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.54.0/23 | 512 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.56.0/22 | 1,024 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.60.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.61.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.62.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.64.0/18 | 16,384 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.128.0/20 | 4,096 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.144.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.148.0/22 | 1,024 | FR-NCNUMERICABLE | Dynamic pools | ASSIGNED PA | Feb 16, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.152.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.160.0/20 | 4,096 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.176.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.184.0/22 | 1,024 | FR-NCNUMERICABLE | Dynamic pools | ASSIGNED PA | Feb 16, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.188.0/22 | 1,024 | FR-NCNUMERICABLE | Dynamic pools | ASSIGNED PA | Feb 16, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.192.0/21 | 2,048 | FR-NCNUMERICABLE | Dynamic pools | ASSIGNED PA | Feb 16, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.200.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.208.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.216.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.218.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.219.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.220.0/22 | 1,024 | FR-NCNUMERICABLE | Dynamic pools | ASSIGNED PA | Feb 16, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.224.0/21 | 2,048 | FR-NCNUMERICABLE | Dynamic pools | ASSIGNED PA | Feb 16, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.232.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.240.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.244.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.245.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.246.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.129.248.0/21 | 2,048 | FR-NCNUMERICABLE | Dynamic pools | ASSIGNED PA | Feb 16, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.130.0.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.130.8.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.130.12.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.130.14.0/23 | 512 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.130.16.0/20 | 4,096 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.130.32.0/23 | 512 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.130.34.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.130.36.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.130.40.0/22 | 1,024 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.130.44.0/23 | 512 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.130.46.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.130.47.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.130.48.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.130.56.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.130.60.0/22 | 1,024 | FR-NCNUMERICABLE | Dynamic pools | ASSIGNED PA | Feb 16, 2016 | abuse@ via SFR-USER-DATA |
| └ 77. | 1,792 | SFR-USER-DATA | DSL | ASSIGNED PA | Oct 3, 2019 | abuse@ via SFR-USER-DATA |
| └ 77.130.71.0/24 | 256 | INFRA | Infra SIS Integrale | ASSIGNED PA | Oct 4, 2019 | abuse@ via SFR-USER-DATA |
| └ 77. | 6,912 | SFR-USER-DATA | DSL | ASSIGNED PA | Oct 7, 2019 | abuse@ via SFR-USER-DATA |
| └ 77.130.99.0/24 | 256 | INFRA | Infra SIS Integrale | ASSIGNED PA | Oct 7, 2019 | abuse@ via SFR-USER-DATA |
| └ 77. | 7,168 | SFR-USER-DATA | DSL | ASSIGNED PA | Oct 7, 2019 | abuse@ via SFR-USER-DATA |
| └ 77.130.128.0/21 | 2,048 | FR-NCNUMERICABLE | Dynamic pools | ASSIGNED PA | Feb 16, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.130.136.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.130.144.0/20 | 4,096 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.130.160.0/19 | 8,192 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.130.192.0/18 | 16,384 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.0.0/19 | 8,192 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.32.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.36.0/22 | 1,024 | FR-NCNUMERICABLE | Dynamic pools | ASSIGNED PA | Feb 16, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.40.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.48.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.56.0/22 | 1,024 | FR-NCNUMERICABLE | Dynamic pools | ASSIGNED PA | Feb 16, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.60.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.64.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.72.0/21 | 2,048 | FR-NCNUMERICABLE | Dynamic pools | ASSIGNED PA | Feb 16, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.80.0/22 | 1,024 | FR-NCNUMERICABLE | Dynamic pools | ASSIGNED PA | Feb 16, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.84.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.88.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.96.0/19 | 8,192 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.128.0/18 | 16,384 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.192.0/19 | 8,192 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.224.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.232.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.236.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.237.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.238.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.240.0/22 | 1,024 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.244.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.246.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.247.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.248.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.249.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.250.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.252.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.253.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.131.254.0/23 | 512 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.0.0/22 | 1,024 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.4.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.8.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.16.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.24.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.25.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.26.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.28.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.29.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.30.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.32.0/20 | 4,096 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.48.0/22 | 1,024 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.52.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.53.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.54.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.56.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.64.0/20 | 4,096 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.80.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.84.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.86.0/23 | 512 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.88.0/21 | 2,048 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.96.0/21 | 2,048 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.104.0/22 | 1,024 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.108.0/23 | 512 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.110.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.112.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.113.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.114.0/23 | 512 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.116.0/22 | 1,024 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.120.0/21 | 2,048 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.128.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.136.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.138.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.139.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.140.0/23 | 512 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.142.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.144.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.148.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.149.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.150.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.152.0/23 | 512 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.154.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.156.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.160.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.162.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.163.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.164.0/22 | 1,024 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.168.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.169.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.170.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.172.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.176.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.180.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.182.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.183.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.184.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.188.0/24 | 256 | SFR-USER-DATA-FTTx | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.189.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.190.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.192.0/19 | 8,192 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.224.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.228.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.230.0/23 | 512 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.232.0/22 | 1,024 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.236.0/23 | 512 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.238.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.240.0/21 | 2,048 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.248.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.252.0/23 | 512 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.132.254.0/23 | 512 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.133.0.0/21 | 2,048 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.133.8.0/22 | 1,024 | SFR-USER-DATA-FTTX | FTTx | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.133.12.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.133.16.0/22 | 1,024 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
| └ 77.133.20.0/24 | 256 | SFR-USER-DATA | DSL | ASSIGNED PA | Apr 12, 2016 | abuse@ via SFR-USER-DATA |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
Composition
The types across the prefix's announced space, by addresses.
Announced space
Address share
Announced space
Types across the prefix
524,288 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 491,520 | 94% | 11 | |
| Business | 32,728 | 6.2% | 1,275 | |
| Mobile | 40 | <0.01% | 6 |
Network & registry
Origin network
AS15557
FR
- Name
- Societe Francaise Du Radiotelephone - SFR SA
- Type
- Internet provider
- Registered
- Aug 3, 2000
- Domain
- sfr.fr
- Website
- alticefrance.com/
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Jun 2016
- Current origin since
- Jun 2016 · 10 yr
- Origin networks
- 1
RPKI
Route origin authorizations
IRR
Route objects on the exact prefix
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 77.130.46.0/24 | AS198949 | RADB | SFR France | MAINT-AS198949 | Nov 13, 2023 |
Whois
Registration for this announcement
- Range
- 77.
128. 0. 0/ 11 - Netname
- FR-SFR-20100831
- Registrant
- Societe Francaise Du Radiotelephone - SFR SA
- Registrant country
- FR
- Organization
- Societe Francaise Du Radiotelephone - SFR SA (ORG-VF1-RIPE)
- Org country
- FR
- Type
- ALLOCATED PA
- Created
- Aug 31, 2010
- Updated
- Dec 5, 2024
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- FR
- Delegated
- Aug 31, 2010
- Status
- assigned
Report abuse
Abuse contact
- abuse@
gaoland. net - Name
- Abuse-C Role
- Handle
- AR15368-RIPE