asn.dev

Observed topology

AS25133 MCLAUT-AS

Residential RIPE

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS25133: 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 LLCTransitIPv41,848
AS9002RETN LimitedUnclassifiedIPv4398
AS34549meerfarbig GmbH & Co. KGHostingIPv4132
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv444
AS20485Joint Stock Company TransTeleComUnclassifiedIPv444
AS24482SG.GSHostingIPv444
AS37721Virtual Technologies & SolutionsResidentialIPv444
AS48185team.blue NVUnclassifiedIPv444
AS48362Stadtwerke FeldkirchResidentialIPv444
AS50263A-Systems Sp. z o.o.UnclassifiedIPv444

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS44664TOV company M-TelUnclassifiedIPv4814

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv42,447
AS44664TOV company M-TelUnclassifiedIPv4814
AS9002RETN LimitedUnclassifiedIPv4482
AS34549meerfarbig GmbH & Co. KGHostingIPv4165
AS50263A-Systems Sp. z o.o.UnclassifiedIPv459
AS20485Joint Stock Company TransTeleComUnclassifiedIPv455
AS212024Marc SchmittUnclassifiedIPv455
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv454
AS37721Virtual Technologies & SolutionsResidentialIPv454
AS50300CustodianDC LimitedUnclassifiedIPv454

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-18 10: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.