Skip to main content

AS133637

IDNIC-NMS-ID

PT Nusantara Multimedia Solution Gorontalo

Registry

Authoritative registration data

AS number
133637
Name
IDNIC-NMS-ID
Organisation
PT Nusantara Multimedia Solution Gorontalo
Country
Flag of Indonesia ID Indonesia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS133637
151.247.33.0/24 IPv4 /24 not checked
160.250.238.0/24 IPv4 /24 not checked
2001:df4:c8c0::/48 IPv6 /48 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS133637
Address families
JKT-IX: Main 5,000 Mbps IPv4 · IPv6
OpenIXP / NiCE 1,000 Mbps IPv4

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

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

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS133637 in AS paths

Observed upstreams
Families
AS4787 ASN-CBN 561 750
v4 v6
AS7713 telkomnet-as-ap 259 336
v4
AS7717 OPENIXP-AS-ID-AP 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS133637 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 1
v4

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.