2a09:4c0:f00::/40
AS58057 · Securebit AG
Summary
- BGP Prefix
- 2a09:4c0::/32
- Country
- 🇺🇸 United States
- Domain
- securebit.ch
- Registry
- RIPE_NCC
- ID
- US-SECUREBIT-20201111
- Allocation
- Part of 2a09:4c0::/29
WHOIS
- Network
- 2a09:4c0:f00::/40
- Name
- Securebit Network United States
- Net name
- US-SECUREBIT-20201111
- Organization type
- allocated-by-lir
- Registry
- RIPE_NCC
- Country
- US
Overlapping Ranges
| Range | Source | Holder | Country |
|---|---|---|---|
| 2a00::/11 | WHOIS (RIPE_NCC) | RIPE Network Coordination Center | EU |
| 2a09:4c0::/29 | BGP route | AS58057 Securebit AG | — |
| 2a09:4c0::/29 | WHOIS (RIPE_NCC) | Securebit AG | EU |
| 2a09:4c0::/29 | RIPE_NCC assigned | — | CH |
| 2a09:4c0::/32 | BGP route | AS58057 Securebit AG | — |
| 2a09:4c0::/32 | WHOIS (RIPE_NCC) | Securebit Network Europe | EU |
| 2a09:4c0:f00::/40 | WHOIS (RIPE_NCC) | Securebit Network United States | US |
| 2a09:4c0:fe0::/44 | WHOIS (RIPE_NCC) | Securebit Tunnelbroker United States | US |
| 2a09:4c0:f00::/48 | BGP route | AS58057 Securebit AG | — |
| 2a09:4c0:f00::/48 | WHOIS (RIPE_NCC) | Securebit Network United States | US |
| 2a09:4c0:f0a::/48 | WHOIS (RIPE_NCC) | Securebit Customers United States | US |
| 2a09:4c0:f01::/48 | BGP route | AS58057 Securebit AG | — |
| 2a09:4c0:f01::/48 | WHOIS (RIPE_NCC) | Securebit Network United States | US |
| 2a09:4c0:f02::/48 | BGP route | AS58057 Securebit AG | — |
| 2a09:4c0:f02::/48 | WHOIS (RIPE_NCC) | Securebit Network United States | US |
| 2a09:4c0:fe0::/48 | BGP route | AS58057 Securebit AG | — |
| 2a09:4c0:fe0::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | FR |
| 2a09:4c0:fe0:1ba::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | PL |
| 2a09:4c0:fe0:1d3::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | HK |
| 2a09:4c0:fe0:1d4::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | DE |
| 2a09:4c0:fe0:1d9::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:1da::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:1db::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:1dc::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:1dd::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | TW |
| 2a09:4c0:fe0:1e0::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:1e6::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | TR |
| 2a09:4c0:fe0:1e7::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | TR |
| 2a09:4c0:fe0:1ea::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:1eb::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:1f8::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:1fc::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | CN |
| 2a09:4c0:fe0:1ff::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:21b::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | TW |
| 2a09:4c0:fe0:21f::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | HU |
| 2a09:4c0:fe0:22f::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:23a::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:23b::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:24b::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:28::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:93::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | CA |
| 2a09:4c0:fe0:172::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | GB |
| 2a09:4c0:fe0:206::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:214::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | GB |
| 2a09:4c0:fe0:218::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | HK |
| 2a09:4c0:fe0:219::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | HK |
| 2a09:4c0:fe0:220::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | HU |
| 2a09:4c0:fe0:227::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:229::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | KR |
| 2a09:4c0:fe0:231::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:232::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:242::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:244::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | CN |
| 2a09:4c0:fe0:ec::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | VI |
| 2a09:4c0:fe0:ed::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:ee::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | US |
| 2a09:4c0:fe0:fd::/64 | WHOIS (RIPE_NCC) | SecurebitTunnelBrokerService | TW |