Data as of Nov 6, 2026
89.212.64.0/18
241 residential-proxy exits · 30 daysT-2, d.o.o.
Residential-proxy exits
Proxy exits
241
1.5% of its addresses · 30 days
Always-on exits
19
7.9% of its exits
Spread
53 of 64
/24s with at least one exit
Providers
85
selling exits here
Oct 7, 2026 – Nov 5, 2026
Exits seen per day
60K observations
- Residential
- Business
/24s with the most always-on exits
Proxy providers listing exits
- 2Captcha
- 711Proxy
- 9Proxy
- AnyIP
- B2Proxy
- BartProxies
- BirdProxies
- BlurPath
- BottingTools
- Bright Data
- BuyingProxy
- ByteProxies
- Byteful
- CatProxies
- CliProxy
- CoreProxy
- DataImpulse
- Datarama
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FloppyData
- GSocks
- Geonix
- Geonode
- GhostConnect
- GloryCloud
- GoProxies
- GonzoProxy
- HydraProxy
- IPCola
- IPFly
- IPOasis
- IPPeak
- IPRoyal
- Infatica
- InfiniteProxies
- KindProxy
- LemonBright
- LightningProxies
- LudaxProxy
- MangoProxy
- MarsProxies
- MoMoProxy
- NSocks
- NextProxy
- NodeMaven
- NodeProxy
- NovProxy
- NovaProxy
- Novada
- Oxylabs
- PSBProxy
- PacketStream
- PrivateByte
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyGeo
- ProxyHat
- ProxyRack
- ProxyWing
- Proxying
- Proxyma
- PuraRoute
- RainProxy
- RapidProxy
- RoamProxy
- RolaProxy
- Shifter
- StrikeProxy
- SwiftProxy
- Thordata
- ThunderProxy
- VantageProxies
- VibeProxies
- VitalData
- VitalExclusive
- VitalProxy
- Webshare
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 |
|---|---|---|---|---|---|---|
| 89.212.0.0/16 | 65,536 | SI-T-2-20060503 | T-2, d.o.o. (ORG-TD6-RIPE) · SI | ALLOCATED PA | May 3, 2006 | abuse@ |
| └ 89.212.64.0/26 | 64 | SI-T-2-EKOINFO | unknown | ASSIGNED PA | Aug 13, 2025 | abuse@ via SI-T-2-20060503 |
| └ 89.212.65.0/29 | 8 | SI-T2-SDL | unknown | ASSIGNED PA | Jan 7, 2019 | abuse@ via SI-T-2-20060503 |
| └ 89.212.65.8/29 | 8 | SI-T2-SENICA | unknown | ASSIGNED PA | Feb 18, 2019 | abuse@ via SI-T-2-20060503 |
| └ 89.212.65.16/28 | 16 | SI-T2-CREA-PRO | Network and Servers | ASSIGNED PA | Nov 9, 2018 | abuse@ via SI-T-2-20060503 |
| └ 89.212.65.32/28 | 16 | SI-T2-ADD | Network and Servers | ASSIGNED PA | Aug 31, 2016 | abuse@ via SI-T-2-20060503 |
| └ 89.212.65.48/29 | 8 | SI-T2-SIBIT | Network and Servers | ASSIGNED PA | Jul 10, 2019 | abuse@ via SI-T-2-20060503 |
| └ 89.212.65.56/29 | 8 | SI-T2-MESO-KAMNIK | Network and Servers | ASSIGNED PA | Aug 31, 2016 | abuse@ via SI-T-2-20060503 |
| └ 89.212.65.80/29 | 8 | SI-T2-INFOMEDIA | unknown | ASSIGNED PA | Jun 15, 2018 | abuse@ via SI-T-2-20060503 |
| └ 89.212.65.88/29 | 8 | SI-T2-KONSULTFIN | unknown | ASSIGNED PA | Jul 25, 2018 | abuse@ via SI-T-2-20060503 |
| └ 89.212.65.96/27 | 32 | SI-T2-TEMIDA | Network and Servers | ASSIGNED PA | Jul 11, 2016 | abuse@ via SI-T-2-20060503 |
| └ 89.212.65.192/29 | 8 | SI-T2-HI-FI | Network and Servers | ASSIGNED PA | Aug 31, 2016 | abuse@ via SI-T-2-20060503 |
| └ 89.212.65.200/29 | 8 | SI-T2-HOTEL-MANAGEMENT | Network and Servers | ASSIGNED PA | Sep 23, 2016 | abuse@ via SI-T-2-20060503 |
| └ 89.212.65.224/27 | 32 | SI-T2-ASAP_ | Network and Servers | ASSIGNED PA | Oct 25, 2016 | abuse@ via SI-T-2-20060503 |
| └ 89.212.66.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Sep 20, 2006 | abuse@ via SI-T-2-20060503 |
| └ 89.212.67.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Sep 20, 2006 | abuse@ via SI-T-2-20060503 |
| └ 89.212.68.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Sep 20, 2006 | abuse@ via SI-T-2-20060503 |
| └ 89.212.69.0/28 | 16 | SI-T2-FOO | unknown | ASSIGNED PA | Dec 16, 2016 | abuse@ via SI-T-2-20060503 |
| └ 89.212.69.16/29 | 8 | SI-T2-SETCCE | unknown | ASSIGNED PA | Dec 16, 2016 | abuse@ via SI-T-2-20060503 |
| └ 89.212.69.32/29 | 8 | SI-T2-SOLCHEM | Network and Servers | ASSIGNED PA | Feb 28, 2014 | abuse@ via SI-T-2-20060503 |
| └ 89.212.69.40/29 | 8 | SI-T-2-DELOITTECE | Network and Servers | ASSIGNED PA | Aug 1, 2014 | abuse@ via SI-T-2-20060503 |
| └ 89.212.69.56/29 | 8 | SI-T2-ADEL | Network and Servers | ASSIGNED PA | Jul 16, 2014 | abuse@ via SI-T-2-20060503 |
| └ 89.212.69.64/26 | 64 | SI-T2-GOOGLE-CACHE | Servers | ASSIGNED PA | Mar 27, 2014 | abuse@ via SI-T-2-20060503 |
| └ 89.212.69.128/29 | 8 | SI-T-2-SPITZER | Network and Servers | ASSIGNED PA | Jul 16, 2014 | abuse@ via SI-T-2-20060503 |
| └ 89.212.69.136/29 | 8 | SI-T2-RUDNIDIS | Network and Servers | ASSIGNED PA | Jul 23, 2014 | abuse@ via SI-T-2-20060503 |
| └ 89.212.69.144/29 | 8 | SI-T2-KOBAL | Network and Servers | ASSIGNED PA | Jul 16, 2014 | abuse@ via SI-T-2-20060503 |
| └ 89. | 7 | SI-T2-MS3 | Network and Servers | ASSIGNED PA | Jul 16, 2014 | abuse@ via SI-T-2-20060503 |
| └ 89.212.69.160/29 | 8 | SI-T-2-HOTEL-TABOR | Network and Servers | ASSIGNED PA | Jul 16, 2014 | abuse@ via SI-T-2-20060503 |
| └ 89.212.69.176/29 | 8 | SI-T2-LOGICDATA | Network and Servers | ASSIGNED PA | Jul 16, 2014 | abuse@ via SI-T-2-20060503 |
| └ 89.212.69.184/29 | 8 | SI-T2-SALVIOL | Network and Servers | ASSIGNED PA | Jul 23, 2014 | abuse@ via SI-T-2-20060503 |
| └ 89.212.69.192/26 | 64 | SI-T2-BEENIUS | Network and Servers | ASSIGNED PA | Jul 16, 2014 | abuse@ via SI-T-2-20060503 |
| └ 89.212.70.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Sep 20, 2006 | abuse@ via SI-T-2-20060503 |
| └ 89.212.71.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Sep 20, 2006 | abuse@ via SI-T-2-20060503 |
| └ 89.212.72.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Sep 20, 2006 | abuse@ via SI-T-2-20060503 |
| └ 89.212.73.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Sep 20, 2006 | abuse@ via SI-T-2-20060503 |
| └ 89.212.74.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Sep 20, 2006 | abuse@ via SI-T-2-20060503 |
| └ 89.212.75.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Sep 20, 2006 | abuse@ via SI-T-2-20060503 |
| └ 89.212.76.245/32 | 1 | SI-T2-NUTRIS-VIST | Network and Servers | ASSIGNED PA | Apr 25, 2012 | abuse@ via SI-T-2-20060503 |
| └ 89. | 53 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Jul 16, 2009 | abuse@ via SI-T-2-20060503 |
| └ 89.212.77.53/32 | 1 | SI-T2-VIST | Network and Servers | ASSIGNED PA | Aug 29, 2008 | abuse@ via SI-T-2-20060503 |
| └ 89. | 202 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Jul 16, 2009 | abuse@ via SI-T-2-20060503 |
| └ 89.212.78.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Sep 20, 2006 | abuse@ via SI-T-2-20060503 |
| └ 89.212.79.0/24 | 256 | SI-T-2 | unknown | ASSIGNED PA | Sep 20, 2006 | abuse@ via SI-T-2-20060503 |
| └ 89.212.80.0/27 | 32 | SI-T2-RCC-IRC | Razvojni center IRC Celje d.o.o. | ASSIGNED PA | Oct 4, 2006 | abuse@ via SI-T-2-20060503 |
| └ 89.212.80.32/27 | 32 | SI-T2-METALAB | Software solutions | ASSIGNED PA | Oct 19, 2006 | abuse@ via SI-T-2-20060503 |
| └ 89.212.80.64/29 | 8 | SI-T2-SVARC | Network and Servers | ASSIGNED PA | Dec 31, 2019 | abuse@ via SI-T-2-20060503 |
| └ 89.212.80.72/29 | 8 | SI-T2-CAR-TARGET-GROUP | Network and Servers | ASSIGNED PA | Dec 31, 2019 | abuse@ via SI-T-2-20060503 |
| └ 89.212.80.80/29 | 8 | SI-T2-CONTINENTAL | unknown | ASSIGNED PA | Feb 18, 2019 | abuse@ via SI-T-2-20060503 |
| └ 89.212.80.96/29 | 8 | SI-T2-AD-CONSULTING | unknown | ASSIGNED PA | Feb 18, 2019 | abuse@ via SI-T-2-20060503 |
| └ 89. | 7 | SI-T2-ALLDEA | Network and Servers | ASSIGNED PA | Aug 13, 2019 | abuse@ via SI-T-2-20060503 |
| └ 89.212.80.128/28 | 16 | SI-T2-IB-CADDY | Contemporary Information Technologies | ASSIGNED PA | Oct 20, 2006 | abuse@ via SI-T-2-20060503 |
| └ 89.212.80.144/29 | 8 | SI-T2-SCHINDLER | Network and Servers | ASSIGNED PA | Dec 31, 2019 | abuse@ via SI-T-2-20060503 |
| └ 89.212.80.152/29 | 8 | SI-T-2-AGENCIJA-OSKAR | Network and Servers | ASSIGNED PA | Apr 30, 2015 | abuse@ via SI-T-2-20060503 |
| └ 89.212.80.160/27 | 32 | SI-T2-CETRTAPOT | Network an Servers | ASSIGNED PA | Oct 20, 2006 | abuse@ via SI-T-2-20060503 |
| └ 89.212.80.192/27 | 32 | SI-T2-GAMASYSTEM | Network and Servers | ASSIGNED PA | Feb 5, 2009 | abuse@ via SI-T-2-20060503 |
| └ 89.212.80.240/28 | 16 | SI-T2-DC-LJ | Network and Servers | ASSIGNED PA | Aug 13, 2019 | abuse@ via SI-T-2-20060503 |
| └ 89.212.81.0/28 | 16 | SI-T2-ROLAN | Network and Servers | ASSIGNED PA | Aug 23, 2019 | abuse@ via SI-T-2-20060503 |
| └ 89.212.81.16/28 | 16 | SI-T2-SGH | SGH Group Servers | ASSIGNED PA | Dec 4, 2006 | abuse@ via SI-T-2-20060503 |
| └ 89.212.81.32/28 | 16 | SI-T2-OLMA | Network and Servers | ASSIGNED PA | Dec 28, 2009 | abuse@ via SI-T-2-20060503 |
| └ 89.212.81.48/28 | 16 | SI-T-2-SAPIENS | Network and Server | ASSIGNED PA | Oct 8, 2014 | abuse@ via SI-T-2-20060503 |
| └ 89.212.81.64/29 | 8 | SI-T2-TS | Network and Servers | ASSIGNED PA | Dec 31, 2019 | abuse@ via SI-T-2-20060503 |
| └ 89.212.81.72/29 | 8 | SI-T2-TEMIDA | Temida network | ASSIGNED PA | Jan 29, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.81.80/28 | 16 | SI-T2-TECH-SKY | Techno Sky network | ASSIGNED PA | Dec 27, 2006 | abuse@ via SI-T-2-20060503 |
| └ 89.212.81.96/28 | 16 | SI-T2-SELEKT | Hosting service, servers | ASSIGNED PA | Jan 29, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.81.112/28 | 16 | SI-T2-NORDISK | Network and servers | ASSIGNED PA | Feb 1, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.81.128/27 | 32 | SI-T2-3FS | Network and Servers | ASSIGNED PA | May 11, 2011 | abuse@ via SI-T-2-20060503 |
| └ 89.212.81.168/29 | 8 | SI-T2-ABELIUM | Network and Servers | ASSIGNED PA | Dec 31, 2019 | abuse@ via SI-T-2-20060503 |
| └ 89.212.81.176/28 | 16 | SI-T2-GORENJE-ORODJARNA | Network and Servers | ASSIGNED PA | Feb 15, 2012 | abuse@ via SI-T-2-20060503 |
| └ 89.212.81.192/28 | 16 | SI-T2-PIKANET | Network and servers | ASSIGNED PA | Mar 21, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.81.208/28 | 16 | SI-T2-CHING-HAI | Network and Servers | ASSIGNED PA | Mar 21, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.81.224/28 | 16 | SI-T2-ZELENIKA | unknown | ASSIGNED PA | Apr 10, 2017 | abuse@ via SI-T-2-20060503 |
| └ 89.212.81.240/28 | 16 | SI-T2-VIRTCOM | Network and Servers | ASSIGNED PA | May 22, 2012 | abuse@ via SI-T-2-20060503 |
| └ 89.212.82.0/27 | 32 | SI-T2-FIDURO | Network and Servers | ASSIGNED PA | Apr 9, 2019 | abuse@ via SI-T-2-20060503 |
| └ 89.212.82.96/27 | 32 | SI-T2-HRUSKA | Network and Servers | ASSIGNED PA | Sep 25, 2009 | abuse@ via SI-T-2-20060503 |
| └ 89.212.82.128/29 | 8 | SI-T2-COMTRADE | Network and Servers | ASSIGNED PA | Aug 13, 2015 | abuse@ via SI-T-2-20060503 |
| └ 89.212.82.144/28 | 16 | SI-T2-BSEMI | Servers and Routers | ASSIGNED PA | Mar 22, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.82.160/27 | 32 | SI-T2-VALTREKS | hosting and integrator | ASSIGNED PA | Mar 26, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.82.192/26 | 64 | SI-T2-ENDRA | Network and Servers | ASSIGNED PA | Feb 12, 2013 | abuse@ via SI-T-2-20060503 |
| └ 89.212.83.0/24 | 256 | SI-T2-JAPTI | JAPTI network | ASSIGNED PA | Mar 29, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.84.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Sep 5, 2012 | abuse@ via SI-T-2-20060503 |
| └ 89.212.85.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Sep 5, 2012 | abuse@ via SI-T-2-20060503 |
| └ 89.212.86.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Sep 5, 2012 | abuse@ via SI-T-2-20060503 |
| └ 89.212.87.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Sep 5, 2012 | abuse@ via SI-T-2-20060503 |
| └ 89.212.88.0/24 | 256 | SI-T-2 | T-2 Core Network | ASSIGNED PA | Mar 12, 2008 | abuse@ via SI-T-2-20060503 |
| └ 89.212.89.0/24 | 256 | SI-T-2 | T-2 WEB hosting | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.90.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.91.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.92.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Sep 5, 2012 | abuse@ via SI-T-2-20060503 |
| └ 89.212.93.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Sep 5, 2012 | abuse@ via SI-T-2-20060503 |
| └ 89.212.94.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Sep 5, 2012 | abuse@ via SI-T-2-20060503 |
| └ 89.212.95.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Sep 5, 2012 | abuse@ via SI-T-2-20060503 |
| └ 89.212.96.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.97.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.98.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.99.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.100.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.101.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.102.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.103.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.104.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.105.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.106.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.107.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.108.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.109.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.110.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.111.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.112.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.113.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.114.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.115.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.117.32/27 | 32 | SI-T2-PROJEKT_ | Network and Servers | ASSIGNED PA | May 21, 2010 | abuse@ via SI-T-2-20060503 |
| └ 89.212.117.64/27 | 32 | SI-T2-ILAB | Network and Servers | ASSIGNED PA | Feb 7, 2011 | abuse@ via SI-T-2-20060503 |
| └ 89.212.118.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.119.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.120.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.121.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.122.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.123.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.124.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.125.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.126.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
| └ 89.212.127.0/24 | 256 | SI-T-2 | T-2 Access Network | ASSIGNED PA | Nov 6, 2007 | abuse@ via SI-T-2-20060503 |
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
16,384 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 14,907 | 91% | 21 | |
| Business | 1,221 | 7.5% | 67 | |
| Internet provider | 256 | 1.6% | 1 |
Network & registry
Origin network
AS34779
SI
- Name
- T-2, d.o.o.
- Type
- Internet provider
- Registered
- Apr 5, 2005
- Domain
- t-2.net
- Website
- www.t-2.net/
- 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 2006
- Current origin since
- Jun 2006 · 20 yr
- Origin networks
- 1
Whois
Registration for this announcement
- Range
- 89.
212. 0. 0/ 16 - Netname
- SI-T-2-20060503
- Registrant
- T-2, d.o.o.
- Registrant country
- SI
- Organization
- T-2, d.o.o. (ORG-TD6-RIPE)
- Org country
- SI
- Type
- ALLOCATED PA
- Created
- May 3, 2006
- Updated
- Apr 4, 2023
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- SI
- Delegated
- May 3, 2006
- Status
- assigned
Report abuse
Abuse contact
- abuse@
t-2. com - Name
- T-2 D.O.O ABUSE-C ROLE
- Handle
- TDAR2-RIPE