Data as of Nov 10, 2026
2.232.0.0/13
No anonymizer spaceFastweb SpA
Residential-proxy exits
Proxy exits
497
0.09% of its addresses · listed by providers
Always-on exits
60
12% of its exits
Spread
232 of 2,048
/24s with at least one exit
Providers
114
selling exits here
/24s with the most always-on exits
Proxy providers listing exits
- 2Captcha
- 2Extract
- 711Proxy
- 9Proxy
- ASHBURNPROXIES
- Ake.net
- AnyIP
- B2Proxy
- BartProxies
- BirdProxies
- BlurPath
- BottingTools
- Bright Data
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EVOPROXY
- EZProxies
- EnigmaProxy
- Evomi
- FLEETPROXY
- FROXY
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- GeekProxy
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HydraProxy
- IPFly
- IPMUSK
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- KocerRoxy
- Kookey
- LemonBright
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MagneticProxy
- MangoProxy
- MarsProxies
- Maskify
- MoMoProxy
- NSocks
- NextProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYON
- PROXYSCRAPE
- PSBProxy
- PacketStream
- PrivateByte
- PrivateProxy
- Proxio
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- RH7Proxy
- RainProxy
- RapidProxy
- ResiProxies
- RoamProxy
- RolaProxy
- SPYDERPROXY_PREMIUM
- Shifter
- SpyderProxy
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- TrueProxies
- VProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- Webshare
- YumiProxy
- ZENPROXY_LITE
- ZENPROXY_PREMIUM
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 |
|---|---|---|---|---|---|---|
| 2.224.0.0/12 | 1,048,576 | IT-FASTWEB-20101230 | Fastweb SpA (ORG-FA7-RIPE) · IT | ALLOCATED PA | Dec 30, 2010 | abuse@ |
| └ 2.232.0.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Oct 17, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.1.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Oct 19, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.2.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Oct 20, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.3.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Oct 24, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.4.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Oct 24, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.5.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 2101 for | ASSIGNED PA | Oct 24, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.6.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Oct 24, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.7.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Oct 27, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.8.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Oct 27, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.9.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Oct 28, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.10.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Oct 31, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.11.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Oct 31, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.12.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Oct 31, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.13.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 2101 for | ASSIGNED PA | Oct 31, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.14.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Oct 31, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.15.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Oct 31, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.16.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Nov 1, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.17.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Nov 1, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.18.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Nov 1, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.19.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Nov 1, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.20.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Nov 3, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.21.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Nov 4, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.22.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Nov 8, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.23.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Nov 8, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.24.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Nov 9, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.26.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Nov 11, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.27.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 2101 for | ASSIGNED PA | Nov 14, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.28.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Nov 14, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.29.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Nov 14, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.30.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Nov 14, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.31.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Nov 14, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.32.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Nov 15, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.33.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Nov 15, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.34.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Nov 16, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.35.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Nov 16, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.36.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Nov 18, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.37.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3904 for | ASSIGNED PA | Nov 18, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.38.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Nov 21, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.39.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Nov 21, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.40.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Nov 21, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.41.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 2101 for | ASSIGNED PA | Nov 21, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.42.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 2101 for | ASSIGNED PA | Nov 21, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.43.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Nov 21, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.44.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Nov 22, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.45.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Nov 22, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.46.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Nov 23, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.47.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Nov 24, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.48.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Nov 24, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.50.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Nov 24, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.51.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Nov 25, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.52.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Nov 28, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.53.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Nov 28, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.54.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Nov 29, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.55.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Nov 29, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.56.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Nov 29, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.57.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Nov 30, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.58.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 2101 for | ASSIGNED PA | Apr 28, 2020 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.59.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Dec 12, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.60.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Dec 12, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.61.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Dec 8, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.62.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Dec 8, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.63.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Dec 12, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.64.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3603 for | ASSIGNED PA | Dec 12, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.65.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Dec 12, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.66.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Dec 12, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.67.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Dec 12, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.68.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Dec 12, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.69.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Dec 12, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.70.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Dec 12, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.71.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Dec 12, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.72.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Dec 12, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.73.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Dec 12, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.74.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Dec 13, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.75.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 2101 for | ASSIGNED PA | Dec 14, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.76.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Dec 14, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.77.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Dec 14, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.78.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Dec 16, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.79.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Dec 16, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.80.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Dec 16, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.81.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Dec 16, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.82.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Dec 16, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.83.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Dec 19, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.84.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Dec 19, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.85.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Dec 20, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.86.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Dec 20, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.87.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3603 for | ASSIGNED PA | Dec 20, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.88.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Dec 21, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.89.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Dec 22, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.90.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Dec 22, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.91.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Dec 22, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.92.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 2101 for | ASSIGNED PA | Dec 23, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.93.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Dec 28, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.94.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Dec 23, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.95.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 2101 for | ASSIGNED PA | Dec 29, 2011 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.96.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3904 for | ASSIGNED PA | Jan 2, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.97.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Jan 2, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.98.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Jan 3, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.99.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Jan 4, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.100.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Jan 5, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.101.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Jan 5, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.102.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Jan 5, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.104.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Jan 10, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.105.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Jan 10, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.106.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Jan 10, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.107.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Jan 10, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.108.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Jan 13, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.109.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 2101 for | ASSIGNED PA | Jan 13, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.110.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Jan 13, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.111.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Jan 16, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.112.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Jan 16, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.113.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Jan 18, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.114.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Jan 18, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.115.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Jan 19, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.116.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Jan 20, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.117.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Jan 20, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.118.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Jan 23, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.119.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Jan 24, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.120.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 2101 for | ASSIGNED PA | Jan 24, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.121.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Jan 24, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.122.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Jan 24, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.123.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Jan 24, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.124.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Jan 24, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.125.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Jan 25, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.126.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Jan 30, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.127.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Jan 30, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.129.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Jan 30, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.130.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Jan 31, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.131.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3603 for | ASSIGNED PA | Feb 1, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.132.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Feb 2, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.133.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Feb 6, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.134.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Feb 6, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.135.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Feb 6, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.136.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Feb 6, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.137.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Feb 6, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.138.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 2101 for | ASSIGNED PA | Feb 7, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.139.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Feb 7, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.140.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Feb 8, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.141.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Feb 9, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.142.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Feb 9, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.143.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Feb 9, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.144.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Feb 10, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.145.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Feb 10, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.146.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Feb 13, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.147.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Feb 13, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.148.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 2101 for | ASSIGNED PA | Feb 14, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.149.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Feb 14, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.150.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3905 for | ASSIGNED PA | Apr 2, 2019 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.152.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Feb 15, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.153.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Feb 16, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.154.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Feb 16, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.155.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 2101 for | ASSIGNED PA | Feb 17, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.156.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Feb 18, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.157.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Feb 18, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.158.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Feb 18, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.159.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Feb 21, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.160.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Feb 24, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.161.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Sep 11, 2020 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.162.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 2101 for | ASSIGNED PA | Feb 25, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.163.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Feb 26, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.164.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Feb 28, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.165.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Feb 28, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.166.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Feb 28, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.167.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3904 for | ASSIGNED PA | Feb 29, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.168.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Feb 29, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.169.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Mar 1, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.170.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Mar 1, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.172.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Mar 2, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.173.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Mar 2, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.174.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Mar 4, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.175.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Mar 4, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.176.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Mar 6, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.177.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Mar 6, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.178.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Mar 9, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.179.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Mar 9, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.180.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Mar 9, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.181.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Mar 9, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.182.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Mar 10, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.183.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Mar 10, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.184.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 2101 for | ASSIGNED PA | Mar 13, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.185.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Mar 14, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.186.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Mar 15, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.187.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Mar 15, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.188.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3603 for | ASSIGNED PA | Mar 16, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.189.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Mar 16, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.191.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Mar 20, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.192.0/21 | 2,048 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3904 for | ASSIGNED PA | Mar 14, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.200.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Mar 21, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.201.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Mar 21, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.202.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3601 for | ASSIGNED PA | Mar 21, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.203.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Mar 21, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.204.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Mar 25, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.205.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 2101 for | ASSIGNED PA | Mar 26, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.206.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Mar 26, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.207.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Mar 26, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.208.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3903 for | ASSIGNED PA | Apr 10, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.209.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3102 for | ASSIGNED PA | Apr 5, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.210.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3902 for | ASSIGNED PA | Apr 8, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.211.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3101 for | ASSIGNED PA | Apr 11, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.212.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3901 for | ASSIGNED PA | Apr 12, 2012 | abuse@ via IT-FASTWEB-20101230 |
| └ 2.232.213.0/24 | 256 | FASTWEB-L3-PAT_ | PAT/NAT IP addresses POP 3602 for | ASSIGNED PA | Apr 12, 2012 | abuse@ via IT-FASTWEB-20101230 |
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 | 524,232 | >99% | 1,381 | |
| Business | 56 | 0.01% | 5 |
Network & registry
Origin network
AS12874
IT
- Name
- Fastweb SpA
- Type
- Internet provider
- Registered
- Dec 17, 1999
- Domain
- fastweb.it
- Website
- www.fastweb.it
- 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 2011
- Current origin since
- Jun 2011 · 15 yr
- Origin networks
- 1
RPKI
Route origin authorizations
| ROA prefix | ASN | Max len | Anchor | Verdict |
|---|---|---|---|---|
| 2.232.0.0/13 | AS12874 | /13 | RIPE | RPKI valid |
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS12874 | RIPE | Fastweb Networks block | FASTWEB-MNT | Jun 8, 2011 |
IRR inside
Route objects inside
| Prefix | Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|---|
| 2.232.0.0/17 | AS12874 | RIPE | Fastweb Networks block | FASTWEB-MNT | Feb 12, 2018 |
| 2.232.128.0/17 | AS12874 | RIPE | Fastweb Networks block | FASTWEB-MNT | Feb 12, 2018 |
Whois
Registration for this announcement
- Range
- 2.
224. 0. 0/ 12 - Netname
- IT-FASTWEB-20101230
- Registrant
- Fastweb SpA
- Registrant country
- IT
- Organization
- Fastweb SpA (ORG-FA7-RIPE)
- Org country
- IT
- Type
- ALLOCATED PA
- Created
- Dec 30, 2010
- Updated
- Sep 12, 2016
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- IT
- Delegated
- Dec 30, 2010
- Status
- assigned
Report abuse
Abuse contact
- abuse@
fastweb. it - Name
- Fastweb Abuse
- Handle
- FA5264-RIPE