asn.dev

Observed topology

AS56899 GARNET-AS Granat Ukraine LLC

Unclassified RIPE Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS56899: 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
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4239
AS60159EUROLINE UKRAINE LLCUnclassifiedIPv499
AS6939Hurricane Electric LLCTransitIPv458
AS1257Tele2 Sverige ABMobileIPv46
AS34927iFog GmbHHostingIPv46
AS8218Zayo Infrastructure France SAUnclassifiedIPv45
AS24482SG.GSHostingIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS31685TOV Teleradiocompany "TIM"UnclassifiedIPv4240
AS50305Intel-Servis, LLCUnclassifiedIPv460
AS212048Monchulyak SerhiyUnclassifiedIPv44

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS50263A-Systems Sp. z o.o.UnclassifiedIPv4386
AS31685TOV Teleradiocompany "TIM"UnclassifiedIPv4240
AS60159EUROLINE UKRAINE LLCUnclassifiedIPv4194
AS6939Hurricane Electric LLCTransitIPv498
AS50305Intel-Servis, LLCUnclassifiedIPv460
AS1257Tele2 Sverige ABMobileIPv412
AS34927iFog GmbHHostingIPv412
AS8218Zayo Infrastructure France SAUnclassifiedIPv410
AS24482SG.GSHostingIPv410
AS212048Monchulyak SerhiyUnclassifiedIPv44

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.