Skip to main content

AS200177

ATLANTIC-AS-ID

PT Atlantic Aksa Group

Registry

Authoritative registration data

AS number
200177
Name
ATLANTIC-AS-ID
Organisation
PT Atlantic Aksa Group
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS200177
178.83.180.0/23 IPv4 /23 not checked
169.40.151.0/24 IPv4 /24 not checked
178.83.180.0/24 IPv4 /24 RPKI valid
178.83.181.0/24 IPv4 /24 RPKI valid
2a06:9801:88::/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 AS200177
Address families
JKT-IX: Main 1,000 Mbps IPv4 · IPv6

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 AS200177 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS200177 in AS paths

Observed upstreams
Families
AS38158 CBN-AS-ID 319 1,766
v4 v6
AS47311 RIPE-ATHARVA-AS-ID 18 74
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS200177 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 4
v4 v6
AS35280 F5 1 4
v4 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.