asn.dev

Observed topology

AS203759 INTAC-SERVICES

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS203759: 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
AS49808Energie AG Oberoesterreich Services und Digital Solutions GmbHUnclassifiedIPv4 IPv668
AS1299Arelion Sweden ABTransitIPv4 IPv630
AS3356Level 3 Parent, LLCTransitIPv4 IPv625
AS3320Deutsche Telekom AGMobileIPv4 IPv610

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44076INTAC Services GmbHUnclassifiedIPv4 IPv64,064
AS211768INTAC Services GmbHUnclassifiedIPv4 IPv6627

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS44076INTAC Services GmbHUnclassifiedIPv4 IPv64,122
AS1299Arelion Sweden ABTransitIPv4 IPv62,335
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,641
AS211768INTAC Services GmbHUnclassifiedIPv4 IPv6627
AS3320Deutsche Telekom AGMobileIPv4 IPv6603
AS5405Inter.link GmbHUnclassifiedIPv4183
AS49808Energie AG Oberoesterreich Services und Digital Solutions GmbHUnclassifiedIPv4 IPv6120

Provenance

Where this comes from

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