asn.dev

Observed topology

AS42555 OPTIC-COM-EU

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS42555: 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
AS6461Zayo BandwidthTransitIPv4777
AS174Cogent Communications, LLCTransitIPv4384
AS6939Hurricane Electric LLCTransitIPv4171
AS47872Sofia Connect EADUnclassifiedIPv4101
AS8866Vivacom Bulgaria EADResidentialIPv424

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS197929PRONET-COM LTDUnclassifiedIPv4110
AS41946Petros Ltd.UnclassifiedIPv4104
AS204232ALOHA EXPERT EOODUnclassifiedIPv458
AS205808Turbo-Net EOODUnclassifiedIPv458
AS57765Optix JSCUnclassifiedIPv46
AS197304Dilis Grup EOODUnclassifiedIPv45
AS48181Prolan Ltd.UnclassifiedIPv42

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS6461Zayo BandwidthTransitIPv4777
AS174Cogent Communications, LLCTransitIPv4500
AS47872Sofia Connect EADUnclassifiedIPv4287
AS6939Hurricane Electric LLCTransitIPv4211
AS197929PRONET-COM LTDUnclassifiedIPv4110
AS41946Petros Ltd.UnclassifiedIPv4104
AS204232ALOHA EXPERT EOODUnclassifiedIPv458
AS205808Turbo-Net EOODUnclassifiedIPv458
AS8866Vivacom Bulgaria EADResidentialIPv425
AS57765Optix JSCUnclassifiedIPv46

All 12 adjacent →

Provenance

Where this comes from

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