Data as of Nov 10, 2026
2.96.0.0/13
No anonymizer spaceTalkTalk Communications Limited
Residential-proxy exits
Proxy exits
21,244
4.1% of its addresses · listed by providers
Always-on exits
1,691
8.0% of its exits
Spread
1,596 of 2,048
/24s with at least one exit
Providers
130
selling exits here
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 2.98.134.0/24 | 6 | 26 | |
| 2.98.36.0/24 | 6 | 23 | |
| 2.100.49.0/24 | 6 | 21 | |
| 2.98.2.0/24 | 6 | 21 | |
| 2.100.239.0/24 | 6 | 16 | |
| 2.96.70.0/24 | 5 | 28 | |
| 2.98.1.0/24 | 5 | 27 | |
| 2.101.111.0/24 | 5 | 27 | |
| 2.98.8.0/24 | 5 | 27 | |
| 2.102.193.0/24 | 5 | 26 | |
| 2.100.228.0/24 | 5 | 23 | |
| 2.101.126.0/24 | 5 | 23 | |
| 2.98.37.0/24 | 5 | 23 | |
| 2.100.121.0/24 | 5 | 22 | |
| 2.98.13.0/24 | 5 | 22 | |
| 2.98.85.0/24 | 5 | 21 | |
| 2.102.152.0/24 | 5 | 20 | |
| 2.102.198.0/24 | 5 | 20 | |
| 2.98.132.0/24 | 5 | 20 | |
| 2.98.133.0/24 | 5 | 19 | |
| 2.101.138.0/24 | 5 | 17 | |
| 2.99.60.0/24 | 5 | 17 | |
| 2.99.69.0/24 | 5 | 15 | |
| 2.101.11.0/24 | 5 | 15 |
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
- FuseProxy
- GSocks
- GeekProxy
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HPROXY
- HideProxy
- HydraProxy
- IPCola
- IPFly
- IPMUSK
- 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
- PROXYON
- PROXYSCRAPE
- PROXYWING_BASIC
- PSBProxy
- PacketStream
- PrivateByte
- PrivateProxy
- Proxies.fo
- ProxiesVision
- Proxio
- Proxiware
- Proxmint
- Proxy-Cheap
- Proxy-Seller
- Proxy302
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyStyler
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- Q2IP
- QUANTICDATA
- RH7Proxy
- RainProxy
- RapidProxy
- RealProxy
- ResiProxies
- RoamProxy
- RolaProxy
- SPYDERPROXY_BASIC
- SPYDERPROXY_PREMIUM
- Shifter
- Smartproxy
- SpyderProxy
- StrikeProxy
- SwiftProxy
- TalorData
- Thordata
- ThunderProxy
- TrueProxies
- TrustProxy
- VProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- WealthProxies
- 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.96.0.0/13 | 524,288 | UK-OPALNET-20100421 | TalkTalk Communications Limited (ORG-OTIS1-RIPE) · GB | ALLOCATED PA | Apr 21, 2010 | abuse-reports@ |
| └ 2.102.224.0/22 | 1,024 | OPAL-DSL-NPE001-CLC-003 | unknown | ASSIGNED PA | Jan 12, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.102.228.0/22 | 1,024 | OPAL-DSL-NPE001-LUT-003 | unknown | ASSIGNED PA | Jan 12, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.102.232.0/22 | 1,024 | OPAL-DSL-NPE001-NOR-004 | unknown | ASSIGNED PA | Jan 12, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.102.236.0/22 | 1,024 | OPAL-DSL-NPE001-LEI-004 | unknown | ASSIGNED PA | Jan 12, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.102.240.0/22 | 1,024 | OPAL-DSL-NPE001-SOU-006 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.102.244.0/22 | 1,024 | OPAL-DSL-NPE001-SOU-007 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.102.248.0/22 | 1,024 | OPAL-DSL-NPE001-SOU-008 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.102.252.0/22 | 1,024 | OPAL-DSL-NPE001-HOV-007 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.0.0/22 | 1,024 | OPAL-DSL-NPE001-HOV-006 | unknown | ASSIGNED PA | Jan 18, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.4.0/22 | 1,024 | OPAL-DSL-NPE001-COL-006 | unknown | ASSIGNED PA | Jan 18, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.8.0/22 | 1,024 | OPAL-DSL-NPE001-SLO-006 | unknown | ASSIGNED PA | Jan 18, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.12.0/22 | 1,024 | OPAL-DSL-NPE001-HORN-004 | unknown | ASSIGNED PA | Jan 18, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.16.0/22 | 1,024 | OPAL-DSL-NPE001-GUI-004 | unknown | ASSIGNED PA | Jan 18, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.20.0/22 | 1,024 | OPAL-DSL-NPE001-TUN-004 | unknown | ASSIGNED PA | Jan 18, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.24.0/22 | 1,024 | OPAL-DSL-NPE001-IPS-004 | unknown | ASSIGNED PA | Jan 18, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.28.0/22 | 1,024 | OPAL-DSL-NPE001-OXF-004 | unknown | ASSIGNED PA | Jan 18, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.32.0/22 | 1,024 | OPAL-DSL-NPE001-MAI-004 | unknown | ASSIGNED PA | Jan 18, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.36.0/22 | 1,024 | OPAL-DSL-NPE001-CRO-006 | unknown | ASSIGNED PA | Jan 18, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.40.0/22 | 1,024 | OPAL-DSL-NPE001-ASH-006 | unknown | ASSIGNED PA | Jan 18, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.44.0/22 | 1,024 | OPAL-DSL-NPE001-ASH-007 | unknown | ASSIGNED PA | Jan 18, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.48.0/22 | 1,024 | OPAL-DSL-NPE001-PRE-004 | unknown | ASSIGNED PA | Jan 18, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.52.0/22 | 1,024 | OPAL-DSL-NPE001-PRE-005 | unknown | ASSIGNED PA | Jan 18, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.56.0/22 | 1,024 | OPAL-DSL-NPE001-WOL-006 | unknown | ASSIGNED PA | Jan 18, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.60.0/22 | 1,024 | OPAL-DSL-NPE001-WOL-007 | unknown | ASSIGNED PA | Jan 18, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.64.0/22 | 1,024 | OPAL-DSL-NPE001-OLD-006 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.68.0/22 | 1,024 | OPAL-DSL-NPE001-STO-004 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.72.0/22 | 1,024 | OPAL-DSL-NPE001-WRE-004 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.76.0/22 | 1,024 | OPAL-DSL-NPE001-BLA-004 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.80.0/22 | 1,024 | OPAL-DSL-NPE002-BLA-004 | unknown | ASSIGNED PA | Jan 19, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.84.0/22 | 1,024 | OPAL-DSL-NPE001-NOT-004 | unknown | ASSIGNED PA | Jan 18, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.88.0/22 | 1,024 | OPAL-DSL-NPE001-SHE-008 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.92.0/22 | 1,024 | OPAL-DSL-NPE002-SHE-008 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.96.0/22 | 1,024 | OPAL-DSL-NPE001-NEW-008 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.100.0/22 | 1,024 | OPAL-DSL-NPE001-LEE-004 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.104.0/21 | 2,048 | OPAL-DSL-NPE001-NOR-002 | unknown | ASSIGNED PA | Jan 12, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.120.0/23 | 512 | OPAL-DSL-NPE001-IRL-004 | unknown | ASSIGNED PA | Jan 20, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.122.0/23 | 512 | OPAL-DSL-NPE002-IRL-004 | unknown | ASSIGNED PA | Jan 20, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.124.0/23 | 512 | OPAL-DSL-NPE001-BRE-003 | unknown | ASSIGNED PA | Jan 20, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.126.0/23 | 512 | OPAL-DSL-NPE002-BRE-004 | unknown | ASSIGNED PA | Jan 20, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.128.0/23 | 512 | OPAL-DSL-NPE001-POR-004 | unknown | ASSIGNED PA | Jan 20, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.130.0/23 | 512 | OPAL-DSL-NPE001-BEL-004 | unknown | ASSIGNED PA | Jan 20, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.132.0/23 | 512 | OPAL-DSL-NPE001-BIR-004 | unknown | ASSIGNED PA | Jan 20, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.134.0/23 | 512 | OPAL-DSL-NPE002-BIR-004 | unknown | ASSIGNED PA | Jan 20, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.136.0/23 | 512 | OPAL-DSL-NPE001-NEW-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.138.0/23 | 512 | OPAL-DSL-NPE001-MAL-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.140.0/23 | 512 | OPAL-DSL-NPE001-LEE-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.142.0/23 | 512 | OPAL-DSL-NPE002-LEE-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.144.0/23 | 512 | OPAL-DSL-NPE001-NOT-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.146.0/23 | 512 | OPAL-DSL-NPE001-LIN-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.148.0/23 | 512 | OPAL-DSL-NPE001-SHE-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.150.0/23 | 512 | OPAL-DSL-NPE002-SHE-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.152.0/23 | 512 | OPAL-DSL-NPE001-ASH-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.154.0/23 | 512 | OPAL-DSL-NPE001-PRE-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.156.0/23 | 512 | OPAL-DSL-NPE001-BEL-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.158.0/23 | 512 | OPAL-DSL-NPE001-POR-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.160.0/23 | 512 | OPAL-DSL-NPE001-ABE-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.162.0/23 | 512 | OPAL-DSL-NPE001-GLA-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.164.0/23 | 512 | OPAL-DSL-NPE001-EDI-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.166.0/23 | 512 | OPAL-DSL-NPE002-EDI-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.168.0/23 | 512 | OPAL-DSL-NPE001-WOL-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.170.0/23 | 512 | OPAL-DSL-NPE001-WRE-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.172.0/23 | 512 | OPAL-DSL-NPE001-OLD-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.174.0/23 | 512 | OPAL-DSL-NPE001-STO-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.176.0/23 | 512 | OPAL-DSL-NPE001-BIR-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.178.0/23 | 512 | OPAL-DSL-NPE002-BIR-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.180.0/23 | 512 | OPAL-DSL-NPE001-BRI-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.182.0/23 | 512 | OPAL-DSL-NPE001-CMC-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.184.0/23 | 512 | OPAL-DSL-NPE002-CMC-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.186.0/23 | 512 | OPAL-DSL-NPE001-GLO-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.188.0/23 | 512 | OPAL-DSL-NPE001-SWA-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.190.0/23 | 512 | OPAL-DSL-NPE001-NPT-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.192.0/23 | 512 | OPAL-DSL-NPE001-YEO-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.194.0/23 | 512 | OPAL-DSL-NPE001-PLY-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.196.0/23 | 512 | OPAL-DSL-NPE001-LEI-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.198.0/23 | 512 | OPAL-DSL-NPE001-NOR-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.200.0/23 | 512 | OPAL-DSL-NPE001-MIL-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.202.0/23 | 512 | OPAL-DSL-NPE001-BRE-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.204.0/23 | 512 | OPAL-DSL-NPE002-BRE-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.206.0/23 | 512 | OPAL-DSL-NPE001-COL-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.208.0/23 | 512 | OPAL-DSL-NPE002-COL-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.210.0/23 | 512 | OPAL-DSL-NPE001-SLO-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.212.0/23 | 512 | OPAL-DSL-NPE001-EAL-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.214.0/23 | 512 | OPAL-DSL-NPE001-KIN-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.216.0/23 | 512 | OPAL-DSL-NPE001-BER-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.218.0/23 | 512 | OPAL-DSL-NPE001-SOU-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.220.0/23 | 512 | OPAL-DSL-NPE001-HOV-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.222.0/23 | 512 | OPAL-DSL-NPE001-GUI-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.224.0/23 | 512 | OPAL-DSL-NPE001-FAR-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.226.0/23 | 512 | OPAL-DSL-NPE001-STE-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.228.0/23 | 512 | OPAL-DSL-NPE001-HORN-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.230.0/23 | 512 | OPAL-DSL-NPE001-WOOD-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.232.0/23 | 512 | OPAL-DSL-NPE001-MAI-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.234.0/23 | 512 | OPAL-DSL-NPE001-TUN-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.236.0/23 | 512 | OPAL-DSL-NPE001-CRO-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.238.0/23 | 512 | OPAL-DSL-NPE001-CAM-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.240.0/23 | 512 | OPAL-DSL-NPE001-IPS-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.242.0/23 | 512 | OPAL-DSL-NPE001-CLC-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.244.0/23 | 512 | OPAL-DSL-NPE001-OXF-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.246.0/23 | 512 | OPAL-DSL-NPE001-LUT-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.248.0/23 | 512 | OPAL-DSL-NPE001-IRL-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.250.0/23 | 512 | OPAL-DSL-NPE002-IRL-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.252.0/23 | 512 | OPAL-DSL-NPE001-BLA-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
| └ 2.103.254.0/23 | 512 | OPAL-DSL-NPE002-BLA-FTTX01 | unknown | ASSIGNED PA | Jan 21, 2011 | abuse-reports@ via UK-OPALNET-20100421 |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
Network & registry
Origin network
AS13285
GB
- Name
- TalkTalk Communications Limited
- Type
- Internet provider
- Registered
- May 25, 2000
- Domain
- pxc.co.uk
- Website
- www.pxc.co.uk/
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Apr 2010
- Current origin since
- Apr 2010 · 17 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 |
|---|---|---|---|---|---|
| 2.96.0.0/14 | AS13285 | RIPE | TalkTalk Communications Limited | TALKTALK-MNT | Feb 7, 2025 |
| 2.100.0.0/14 | AS13285 | RIPE | TalkTalk Communications Limited | TALKTALK-MNT | Feb 7, 2025 |
Whois
Registration for this announcement
- Range
- 2.
96. 0. 0/ 13 - Netname
- UK-OPALNET-20100421
- Registrant
- TalkTalk Communications Limited
- Registrant country
- GB
- Organization
- TalkTalk Communications Limited (ORG-OTIS1-RIPE)
- Org country
- GB
- Type
- ALLOCATED PA
- Created
- Apr 21, 2010
- Updated
- Feb 7, 2025
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- GB
- Delegated
- Apr 21, 2010
- Status
- assigned
Report abuse
Abuse contact
- abuse-reports@
pxc. co. uk - Name
- TalkTalk Abuse Team
- Handle
- TTAT1-RIPE