asn.dev

Observed topology

AS211186 FastTelecomGR FAST TELECOM SINGLE MEMBER P.C.

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS211186: 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
AS6939Hurricane Electric LLCTransitIPv4175
AS174Cogent Communications, LLCTransitIPv4 IPv6149
AS57463NetIX Communications JSCUnclassifiedIPv4 IPv694
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv63
AS24482SG.GSHostingIPv63
AS34019Hivane AssociationUnclassifiedIPv63
AS34549meerfarbig GmbH & Co. KGHostingIPv63
AS401753BIXCE IncUnclassifiedIPv63

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS398987PhirePhly DesignHostingIPv4 IPv68

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4175
AS174Cogent Communications, LLCTransitIPv4 IPv6152
AS57463NetIX Communications JSCUnclassifiedIPv4 IPv696
AS398987PhirePhly DesignHostingIPv4 IPv68
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv64
AS34549meerfarbig GmbH & Co. KGHostingIPv64
AS401753BIXCE IncUnclassifiedIPv64
AS24482SG.GSHostingIPv63
AS34019Hivane AssociationUnclassifiedIPv63

Provenance

Where this comes from

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