AS134599
DIGITALDOTNET-AS-AP
Digital Dot Net (DDN)
Registry
Authoritative registration data
- AS number
- 134599
- Name
- DIGITALDOTNET-AS-AP
- Organisation
- Digital Dot Net (DDN)
- Country
-
BD
Bangladesh
- RIR
- APNIC
- Registered
IPv4 prefixes
10
IPv6 prefixes
16
Total announced
26
Announced prefixes
Observed in BGP by route collectors, not a registry allocation list
| 103.121.36.0/24 | IPv4 | /24 | not checked | |
| 103.121.37.0/24 | IPv4 | /24 | not checked | |
| 103.121.38.0/24 | IPv4 | /24 | not checked | |
| 103.121.39.0/24 | IPv4 | /24 | not checked | |
| 103.135.91.0/24 | IPv4 | /24 | not checked | |
| 103.136.107.0/24 | IPv4 | /24 | not checked | |
| 103.140.204.0/24 | IPv4 | /24 | not checked | |
| 103.177.139.0/24 | IPv4 | /24 | not checked | |
| 103.179.58.0/24 | IPv4 | /24 | not checked | |
| 103.70.170.0/24 | IPv4 | /24 | not checked | |
| 2404:5fc0:1000::/36 | IPv6 | /36 | RPKI valid | |
| 2404:5fc0:2000::/36 | IPv6 | /36 | RPKI valid | |
| 2404:5fc0:3000::/36 | IPv6 | /36 | RPKI valid | |
| 2404:5fc0:4000::/36 | IPv6 | /36 | RPKI valid | |
| 2404:5fc0:5000::/36 | IPv6 | /36 | RPKI valid | |
| 2404:5fc0:6000::/36 | IPv6 | /36 | RPKI valid | |
| 2404:5fc0:7000::/36 | IPv6 | /36 | RPKI valid | |
| 2404:5fc0:8000::/36 | IPv6 | /36 | RPKI valid | |
| 2404:5fc0:9000::/36 | IPv6 | /36 | RPKI valid | |
| 2404:5fc0::/36 | IPv6 | /36 | RPKI valid | |
| 2404:5fc0:a000::/36 | IPv6 | /36 | not checked | |
| 2404:5fc0:b000::/36 | IPv6 | /36 | not checked | |
| 2404:5fc0:c000::/36 | IPv6 | /36 | not checked | |
| 2404:5fc0:d000::/36 | IPv6 | /36 | not checked | |
| 2404:5fc0:e000::/36 | IPv6 | /36 | not checked | |
| 2404:5fc0:f000::/36 | IPv6 | /36 | RPKI valid |
No rows match “”.
Showing – of
Internet Exchanges
Exchanges where this network has a listed peering LAN connection
| Address families | ||
|---|---|---|
| AIX-BD: Main | 10,000 Mbps | IPv4 |
| BDIX: Main | 10,000 Mbps | IPv4 |
| ISPAB-NIX | 10,000 Mbps | IPv4 |
No rows match “”.
Showing – of
Exchange membership means the network has a listed connection; it does not prove peering with other members.
Observed adjacencies
No adjacency data available
Route collectors reported no AS path data for this network, or the routing data source was unavailable.