asn.dev

Observed topology

AS49849 MG2002-AS

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS49849: 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
AS57344Telehouse EADResidentialIPv4966
AS12615Global Communication Net PlcUnclassifiedIPv4228
AS8262Evolink EADUnclassifiedIPv4201
AS6939Hurricane Electric LLCTransitIPv4192
AS29084Comnet Bulgaria Holding Ltd.ResidentialIPv4180
AS34224Neterra Ltd.UnclassifiedIPv4122
AS35122Satnet LTDUnclassifiedIPv412
AS59900Balkan Internet Exchange LtdUnclassifiedIPv41

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS57344Telehouse EADResidentialIPv4966
AS12615Global Communication Net PlcUnclassifiedIPv4228
AS8262Evolink EADUnclassifiedIPv4201
AS6939Hurricane Electric LLCTransitIPv4192
AS29084Comnet Bulgaria Holding Ltd.ResidentialIPv4180
AS34224Neterra Ltd.UnclassifiedIPv4122
AS35122Satnet LTDUnclassifiedIPv412
AS59900Balkan Internet Exchange LtdUnclassifiedIPv41

Provenance

Where this comes from

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