asn.dev

Observed topology

AS35761 TIVI_BG Mitko.Com Ltd.

Unclassified RIPE NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS35761: 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 LLCTransitIPv4 IPv6551
AS57344Telehouse ADResidentialIPv4 IPv6148
AS3303Swisscom (Schweiz) AGResidentialIPv47
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv46
AS44901Belcloud LTDHostingIPv45

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS41782BGLAN LTDUnclassifiedIPv4179
AS48698Net IP Ltd.UnclassifiedIPv4164
AS199230Mitko.com EOODUnclassifiedIPv456
AS48264Mitko.Com Ltd.UnclassifiedIPv636

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6920
AS57344Telehouse ADResidentialIPv4 IPv6192
AS41782BGLAN LTDUnclassifiedIPv4179
AS48698Net IP Ltd.UnclassifiedIPv4164
AS199230Mitko.com EOODUnclassifiedIPv456
AS48264Mitko.Com Ltd.UnclassifiedIPv636
AS44901Belcloud LTDHostingIPv416
AS3303Swisscom (Schweiz) AGResidentialIPv411
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv49
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv4 IPv64

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.