asn.dev

Observed topology

AS55655 SIMS-AS-ID - PT. Saranainsan Mudaselaras

Unclassified ARIN

Upstreams 0 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 11
Adjacent (IPv6) 7
Upstream graph Who carries AS55655, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS55655 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS55655: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

Networks for which AS55655 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS64315PT MITRA VISIONER PRATAMAUnclassifiedIPv474

Adjacency

Adjacent networks

All 12

Every AS seen directly next to AS55655 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS38001NewMedia Express Pte LtdHostingIPv4 IPv6546
AS147094PT. MITRA VISIONER PRATAMAUnclassifiedIPv4 IPv6546
AS64315PT MITRA VISIONER PRATAMAUnclassifiedIPv4 IPv6305
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv6154
AS6939Hurricane Electric LLCTransitIPv4 IPv671
AS33891Core-Backbone GmbHHostingIPv441
AS9930TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, MalaysiaUnclassifiedIPv422
AS8966EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSCMobileIPv4 IPv66
AS55818MC-IX Matrix Internet Exchange RS-1ResidentialIPv44
AS24482SG.GSHostingIPv42

All 12 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.