Skip to main content

AS400146

DIAMOND-STATE-NETWORKS

DIAMOND STATE NETWORKS, LLC

Registry

Authoritative registration data

AS number
400146
Name
DIAMOND-STATE-NETWORKS
Organisation
DIAMOND STATE NETWORKS, LLC
Country
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS400146
66.33.24.0/21 IPv4 /21 not checked
66.33.80.0/21 IPv4 /21 not checked
23.136.136.0/24 IPv4 /24 not checked
2606:d240::/32 IPv6 /32 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Observed adjacencies

Networks seen next to AS400146 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS400146 in AS paths

Observed upstreams
Families
AS6939 3,655 35,460
v4 v6
AS174 372 2,908
v4 v6
AS3257 227 1,745
v4 v6
AS2914 230 1,621
v4 v6
AS25091 42 595
v4 v6
AS971 15 114
v4
AS137409 14 108
v4
AS4230 13 98
v4
AS23404 4 36
v4
AS395662 11 33
v4 v6
AS286 8 8
v6

No rows match “”.

Showing of

Observed downstreams

13 networks seen after AS400146 in AS paths

Observed downstreams
Families
AS399493 322 12,551
v4 v6
AS22413 847 10,375
v4 v6
AS22280 327 3,793
v4 v6
AS395862 288 2,672
v4
AS398536 291 2,655
v4
AS32458 324 2,342
v4 v6
AS399331 546 1,898
v4 v6
AS36556 157 1,784
v4
AS399554 339 1,508
v4 v6
AS33294 341 1,507
v4 v6
AS400674 338 746
v4 v6
AS398159 248 332
v4
AS396287 15 100
v4

No rows match “”.

Showing of

Uncertain adjacencies

9 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS19151 15 220
v4 v6
AS49544 13 148
v4 v6
AS14907 15 122
v4 v6
AS1003 16 120
v4 v6
AS1828 15 116
v4 v6
AS36236 14 112
v4 v6
AS34927 16 111
v4 v6
AS35280 14 99
v4
AS200454 10 10
v6

No rows match “”.

Showing of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.