Data as of Nov 8, 2026
213.164.192.0/19
61 residential-proxy exits · 30 daysBahnhof AB
Residential-proxy exits
Proxy exits
61
0.74% of its addresses · 30 days
Always-on exits
3
4.9% of its exits
Spread
20 of 32
/24s with at least one exit
Providers
62
selling exits here
Oct 9, 2026 – Nov 7, 2026
Exits seen per day
7.7K observations
- Residential
- Business
/24s with the most always-on exits
Proxy providers listing exits
- 2Captcha
- 2Extract
- 711Proxy
- Ake.net
- AnyIP
- B2Proxy
- BirdProxies
- BottingTools
- ByteProxies
- Byteful
- CliProxy
- DataImpulse
- Decodo
- EZProxies
- EnigmaProxy
- Evomi
- FastProxy
- FlashProxy
- FlexyProxies
- FloppyData
- GSocks
- Geonix
- GonzoProxy
- IPFly
- IPOasis
- IPPeak
- Infatica
- LemonBright
- LemonLabs
- LemonPrime
- LightningProxies
- LudaxProxy
- MangoProxy
- NextProxy
- NodeMaven
- NodeProxy
- NovaProxy
- Novada
- Oxylabs
- PROXYWING_BASIC
- Proxiware
- Proxmint
- Proxy-Seller
- Proxy4U
- ProxyEmpire
- ProxyRack
- ProxyWing
- Proxyma
- PuraRoute
- QUANTICDATA
- RainProxy
- SPYDERPROXY_PREMIUM
- Shifter
- StrikeProxy
- Thordata
- ThunderProxy
- VantageProxies
- VibeProxies
- VitalExclusive
- VitalProxy
- Webshare
- 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 |
|---|---|---|---|---|---|---|
| 213.164.192.0/19 | 8,192 | SE-BAHNHOF-20040927 | Bahnhof AB (ORG-BIA1-RIPE) · SE | ALLOCATED PA | Sep 27, 2004 | abuse@ |
| └ 213.164.192.0/29 | 8 | RID-0000650660 | unknown | ASSIGNED PA | Nov 25, 2020 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.192.16/28 | 16 | RID-0000616934 | unknown | ASSIGNED PA | Nov 25, 2020 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.192.64/30 | 4 | RID-0000962593 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.192.68/30 | 4 | RID-0000019909 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.192.72/29 | 8 | RID-0000625925 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.192.80/29 | 8 | RID-0000868292 | unknown | ASSIGNED PA | Dec 1, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.192.88/29 | 8 | RID-0000789335 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.192.96/29 | 8 | RID-0000606707 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.192.104/30 | 4 | RID-0000831590 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.192.108/30 | 4 | RID-0000357525 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.192.112/29 | 8 | RID-0001040502 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.192.120/30 | 4 | RID-0000892183 | unknown | ASSIGNED PA | Jan 5, 2022 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.192.124/30 | 4 | RID-0000114019 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.193.64/30 | 4 | RID-0000254100 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.193.68/30 | 4 | RID-0000503585 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.193.72/30 | 4 | RID-0000715390 | unknown | ASSIGNED PA | Dec 1, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.193.76/30 | 4 | RID-0001033929 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.193.88/29 | 8 | RID-0000902402 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.193.96/30 | 4 | RID-0000459701 | unknown | ASSIGNED PA | Jan 5, 2022 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.193.100/30 | 4 | RID-0000893685 | unknown | ASSIGNED PA | Jan 5, 2022 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.193.104/30 | 4 | RID-0000707419 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.193.108/30 | 4 | RID-0000482860 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.193.112/30 | 4 | RID-0001046963 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.193.116/30 | 4 | RID-0000301709 | unknown | ASSIGNED PA | Nov 25, 2020 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.193.120/30 | 4 | RID-0001019245 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.193.124/30 | 4 | RID-0000834803 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.193.128/25 | 128 | GENERAL-PRIVATE-NET-A444-22 | Dynamic private network | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.194.0/24 | 256 | GENERAL-PRIVATE-NET-A192-16 | Dynamic private network | ASSIGNED PA | Nov 25, 2020 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.195.0/24 | 256 | GENERAL-PRIVATE-NET-A980-10 | Dynamic private network | ASSIGNED PA | Nov 25, 2020 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.196.0/29 | 8 | RID-0000078427 | unknown | ASSIGNED PA | Oct 3, 2023 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.196.8/29 | 8 | RID-0000839819 | unknown | ASSIGNED PA | Oct 3, 2023 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.196.16/29 | 8 | RID-0000335271 | unknown | ASSIGNED PA | Oct 3, 2023 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.196.24/30 | 4 | RID-0000728003 | unknown | ASSIGNED PA | Oct 3, 2023 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.196.28/30 | 4 | RID-0000968738 | unknown | ASSIGNED PA | Oct 3, 2023 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.196.32/27 | 32 | GENERAL-PRIVATE-NET-A498-383 | Dynamic private network | ASSIGNED PA | Oct 3, 2023 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.196.96/30 | 4 | RID-0000966418 | unknown | ASSIGNED PA | Oct 3, 2023 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.196.100/30 | 4 | RID-0000967399 | unknown | ASSIGNED PA | Oct 3, 2023 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.196.168/30 | 4 | RID-0000827801 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.196.172/30 | 4 | RID-0000780627 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.196.184/30 | 4 | RID-0000814168 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.196.188/30 | 4 | RID-0000826989 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.196.224/28 | 16 | RID-0000833669 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.196.240/29 | 8 | RID-0000744631 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.197.0/24 | 256 | GENERAL-PRIVATE-NET-A980-11 | Dynamic private network | ASSIGNED PA | Nov 25, 2020 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.198.0/24 | 256 | GENERAL-PRIVATE-NET-A980-12 | Dynamic private network | ASSIGNED PA | Nov 25, 2020 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.199.0/24 | 256 | GENERAL-PRIVATE-NET-A357-65 | Dynamic private network | ASSIGNED PA | Nov 25, 2020 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.201.0/24 | 256 | GENERAL-PRIVATE-NET-A980-13 | Dynamic private network | ASSIGNED PA | Nov 25, 2020 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.202.32/27 | 32 | GENERAL-PRIVATE-NET-A498-281 | Dynamic private network | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.203.0/24 | 256 | GENERAL-PRIVATE-NET-A158-13 | Dynamic private network | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.204.0/22 | 1,024 | RID-0000255024 | unknown | ASSIGNED PA | Nov 25, 2020 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.208.0/27 | 32 | RID-0000873271 | unknown | ASSIGNED PA | Oct 3, 2023 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.208.48/29 | 8 | RID-0000723951 | unknown | ASSIGNED PA | Oct 3, 2023 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.208.56/30 | 4 | RID-0000957246 | unknown | ASSIGNED PA | Oct 3, 2023 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.208.60/30 | 4 | RID-0000212517 | unknown | ASSIGNED PA | Oct 3, 2023 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.211.0/24 | 256 | GENERAL-PRIVATE-NET-A980-14 | Dynamic private network | ASSIGNED PA | Nov 25, 2020 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.212.0/24 | 256 | RID-0000671686 | unknown | ASSIGNED PA | Nov 25, 2020 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.214.0/24 | 256 | GENERAL-PRIVATE-NET-A980-15 | Dynamic private network | ASSIGNED PA | Nov 25, 2020 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.216.0/29 | 8 | RID-0000601925 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.216.8/30 | 4 | RID-0000900810 | unknown | ASSIGNED PA | Mar 9, 2022 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.216.12/30 | 4 | RID-0000900810 | unknown | ASSIGNED PA | Mar 9, 2022 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.216.16/30 | 4 | RID-0000337598 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.216.20/30 | 4 | RID-0000800242 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.216.24/29 | 8 | RID-0000577955 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.216.64/27 | 32 | RID-0000158302 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.216.96/30 | 4 | RID-0000836957 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.216.100/30 | 4 | RID-0000609931 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.216.104/29 | 8 | RID-0000833063 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.217.0/24 | 256 | GENERAL-PRIVATE-NET-A357-66 | Dynamic private network | ASSIGNED PA | Nov 25, 2020 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.218.0/25 | 128 | GENERAL-PRIVATE-NET-A240-27 | Dynamic private network | ASSIGNED PA | Dec 21, 2020 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.218.192/26 | 64 | GENERAL-PRIVATE-NET-A400-46 | Dynamic private network | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.219.0/28 | 16 | GENERAL-PRIVATE-NET-A498-479 | Dynamic private network | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.219.16/28 | 16 | RID-0000966538 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.219.32/27 | 32 | GENERAL-PRIVATE-NET-A498-480 | Dynamic private network | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.219.64/27 | 32 | GENERAL-PRIVATE-NET-A498-481 | Dynamic private network | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.219.96/29 | 8 | RID-0000744374 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.219.104/30 | 4 | RID-0000353247 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.219.108/30 | 4 | RID-0001047665 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.219.120/30 | 4 | RID-0000018829 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.219.124/30 | 4 | RID-0000848519 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.219.128/30 | 4 | RID-0000777087 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.219.132/30 | 4 | RID-0000243642 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.219.136/30 | 4 | RID-0001047701 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.219.144/29 | 8 | RID-0001025768 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.219.152/29 | 8 | RID-0000285148 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.219.160/28 | 16 | GENERAL-CORPORATE-NET-A1807-6 | Dynamic corporate network | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.219.176/28 | 16 | GENERAL-CORPORATE-NET-A1807-7 | Dynamic corporate network | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.219.192/26 | 64 | GENERAL-PRIVATE-NET-A498-482 | Dynamic private network | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.221.0/26 | 64 | GENERAL-PRIVATE-NET-A400-47 | Dynamic private network | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.221.112/30 | 4 | RID-0000507912 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.221.116/30 | 4 | RID-0000428020 | unknown | ASSIGNED PA | Jan 5, 2022 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.221.120/30 | 4 | RID-0000529050 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.221.124/30 | 4 | RID-0000638544 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.221.128/25 | 128 | GENERAL-PRIVATE-NET-A240-28 | Dynamic private network | ASSIGNED PA | Dec 21, 2020 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.222.40/30 | 4 | RID-0000308086 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.222.44/30 | 4 | RID-0000518873 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.222.48/30 | 4 | RID-0000517618 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.222.52/30 | 4 | RID-0000441723 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.222.64/30 | 4 | RID-0001033929 | unknown | ASSIGNED PA | Aug 26, 2024 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.222.68/30 | 4 | RID-0000869877 | unknown | ASSIGNED PA | Dec 1, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.222.104/29 | 8 | RID-0000837540 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.222.112/30 | 4 | RID-0000838484 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.222.116/30 | 4 | RID-0000833378 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.222.120/29 | 8 | RID-0000639002 | unknown | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.222.144/28 | 16 | GENERAL-CORPORATE-NET-A400-80 | Dynamic corporate network | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.222.184/29 | 8 | RID-0000171494 | unknown | ASSIGNED PA | Dec 1, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.222.192/30 | 4 | RID-0000778251 | unknown | ASSIGNED PA | Dec 1, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.222.196/30 | 4 | RID-0000870724 | unknown | ASSIGNED PA | Dec 1, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.222.232/29 | 8 | RID-0000863606 | unknown | ASSIGNED PA | Dec 1, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.223.8/30 | 4 | RID-0000866884 | unknown | ASSIGNED PA | Dec 1, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.223.12/30 | 4 | RID-0000307843 | unknown | ASSIGNED PA | Dec 1, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.223.88/30 | 4 | RID-0000273612 | unknown | ASSIGNED PA | Dec 1, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.223.92/30 | 4 | RID-0000055126 | unknown | ASSIGNED PA | Dec 1, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.223.104/30 | 4 | RID-0000337100 | unknown | ASSIGNED PA | Dec 1, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.223.108/30 | 4 | RID-0000866819 | unknown | ASSIGNED PA | Dec 1, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.223.160/29 | 8 | RID-0000250293 | unknown | ASSIGNED PA | Dec 1, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.223.176/28 | 16 | GENERAL-PRIVATE-NET-A498-293 | Dynamic private network | ASSIGNED PA | Dec 1, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.223.192/27 | 32 | GENERAL-PRIVATE-NET-A498-282 | Dynamic private network | ASSIGNED PA | Sep 3, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.223.224/28 | 16 | GENERAL-PRIVATE-NET-A498-294 | Dynamic private network | ASSIGNED PA | Dec 1, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.223.240/30 | 4 | RID-0000857306 | unknown | ASSIGNED PA | Dec 1, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.223.244/30 | 4 | RID-0000902969 | unknown | ASSIGNED PA | Jun 28, 2022 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.223.248/30 | 4 | RID-0000871062 | unknown | ASSIGNED PA | Dec 1, 2021 | abuse@ via SE-BAHNHOF-20040927 |
| └ 213.164.223.252/30 | 4 | RID-0000807590 | unknown | ASSIGNED PA | Dec 1, 2021 | abuse@ via SE-BAHNHOF-20040927 |
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
8,192 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Residential | 7,360 | 90% | 12 | |
| Business | 832 | 10% | 17 |
Network & registry
Origin network
AS8473
SE
- Name
- Bahnhof AB
- Type
- Internet provider
- Registered
- Sep 18, 1997
- Domain
- bahnhof.se
- Website
- www.bahnhof.net/
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
- VPN servers
- 127
- Tor exits
- 2
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- May 2005
- Current origin since
- Sep 2018 · 8.1 yr
- Origin networks
- 2
- Last change of origin
- Sep 2018
Recorded history
History
- Handoffs
- 1
Whois
Registration for this announcement
- Range
- 213.
164. 192. 0/ 19 - Netname
- SE-BAHNHOF-20040927
- Registrant
- Bahnhof AB
- Registrant country
- SE
- Organization
- Bahnhof AB (ORG-BIA1-RIPE)
- Org country
- SE
- Type
- ALLOCATED PA
- Created
- Sep 27, 2004
- Updated
- Jul 3, 2023
- Maintainer
- RIPE-NCC-HM-MNT
- RIR
- RIPE NCC
- Country
- SE
- Delegated
- Sep 27, 2004
- Status
- assigned
Report abuse
Abuse contact
- abuse@
bahnhof. net - Name
- Abuse-C Role
- Handle
- AR13477-RIPE