asn.dev

Observed topology

AS45630 FIBRECOMM-MY AS-FIBRECOMM-MY- Internet Service Provider

Residential APNIC

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS45630: 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.

ASNetworkTypeFamiliesPaths seen
AS4788TM TECHNOLOGY SERVICES SDN. BHD.MobileIPv4 IPv662
AS56308TELEKOMUNIKASI INDONESIA INTERNATIONAL, PTE.LTDUnclassifiedIPv4 IPv615
AS6939Hurricane Electric LLCTransitIPv48
AS1299Arelion Sweden ABTransitIPv66
AS24482SG.GSHostingIPv4 IPv62
AS55720Gigabit Hosting Sdn BhdHostingIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS55951Lembaga Hasil Dalam Negeri MalaysiaUnclassifiedIPv4180
AS38006Time Quantum Technologies Sdn. Bhd.UnclassifiedIPv415

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS55951Lembaga Hasil Dalam Negeri MalaysiaUnclassifiedIPv4180
AS56308TELEKOMUNIKASI INDONESIA INTERNATIONAL, PTE.LTDUnclassifiedIPv4 IPv6102
AS1299Arelion Sweden ABTransitIPv4 IPv688
AS4788TM TECHNOLOGY SERVICES SDN. BHD.MobileIPv4 IPv674
AS6939Hurricane Electric LLCTransitIPv424
AS38006Time Quantum Technologies Sdn. Bhd.UnclassifiedIPv415
AS9930TIME dotCom Berhad No. 14, Jalan Majistret U1/26 Hicom Glenmarie Industrial Park 40150 Shah Alam Selangor, MalaysiaUnclassifiedIPv48
AS55720Gigabit Hosting Sdn BhdHostingIPv45
AS24482SG.GSHostingIPv4 IPv64

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-22 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.12M 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.