Skip to main content

AS135659

IDNIC-DETNET-AS-ID

PT Detroit Network Indonesia

Registry

Authoritative registration data

AS number
135659
Name
IDNIC-DETNET-AS-ID
Organisation
PT Detroit Network Indonesia
Country
Flag of Indonesia ID Indonesia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

10

Total announced

11

Announced prefixes

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

Prefixes announced by AS135659
160.250.227.0/24 IPv4 /24 RPKI valid
2a14:7581:4940::/44 IPv6 /44 RPKI valid
2001:df4:c6c0::/48 IPv6 /48 RPKI valid
2a14:7581:4942::/48 IPv6 /48 RPKI valid
2a14:7581:4943::/48 IPv6 /48 not checked
2a14:7581:4944::/48 IPv6 /48 not checked
2a14:7581:4945::/48 IPv6 /48 not checked
2a14:7581:4946::/48 IPv6 /48 not checked
2a14:7581:4947::/48 IPv6 /48 not checked
2a14:7581:4948::/48 IPv6 /48 not checked
2a14:7581:4949::/48 IPv6 /48 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Observed adjacencies

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

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS135659 in AS paths

Observed upstreams
Families
AS6939 659 3,056
v6
AS52025 245 1,080
v6
AS47311 311 1,053
v4 v6
AS138128 266 890
v4 v6
AS58389 113 145
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS135659 in AS paths

Observed downstreams
Families
AS215171 511 2,210
v6

No rows match “”.

Showing of

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 3 14
v4 v6
AS35280 3 14
v4 v6
AS38001 1 8
v4 v6
AS199524 1 8
v4 v6
AS1828 1 7
v6
AS45489 1 7
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.