asn.dev

Observed topology

AS42459 FOBUL Fiber Optics Bulgaria OOD

Unclassified RIPE NSP

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

Transit

Upstream networks

All 22

Networks observed carrying traffic for AS42459: 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
AS2914NTT America, Inc.TransitIPv4135
AS6939Hurricane Electric LLCTransitIPv4 IPv688
AS31287IPACCT CABLE LtdUnclassifiedIPv456
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv625
AS3257GTT Communications Inc.TransitIPv410
AS12859BIT BVHostingIPv4 IPv69
AS24482SG.GSHostingIPv4 IPv69
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv69
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv69
AS212024Marc SchmittUnclassifiedIPv4 IPv69

All 22 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS25076KTV Istar Ltd.UnclassifiedIPv432

Adjacency

Adjacent networks

All 23

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

ASNetworkTypeFamiliesPaths seen
AS2914NTT America, Inc.TransitIPv4135
AS6939Hurricane Electric LLCTransitIPv4 IPv696
AS31287IPACCT CABLE LtdUnclassifiedIPv463
AS25076KTV Istar Ltd.UnclassifiedIPv432
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv628
AS3257GTT Communications Inc.TransitIPv410
AS12859BIT BVHostingIPv4 IPv610
AS24482SG.GSHostingIPv4 IPv610
AS42708Glesys Sweden ABUnclassifiedIPv4 IPv610
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv610

All 23 adjacent →

Provenance

Where this comes from

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