asn.dev

Observed topology

AS210825 TEIGTASCHERLFABRIK

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS210825: 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
AS11967Hop179 OUUnclassifiedIPv6155
AS215296Raoul Brouns is trading as LowPing NLUnclassifiedIPv4 IPv681
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv66
AS58057Securebit AGUnclassifiedIPv65
AS4913410VPN Research Network LTDUnclassifiedIPv41
AS212508Lowhosting services of Davide GennariUnclassifiedIPv41

Transit

Downstream networks

inferred

Networks for which AS210825 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 AS210825 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS11967Hop179 OUUnclassifiedIPv6155
AS215296Raoul Brouns is trading as LowPing NLUnclassifiedIPv4 IPv681
AS37989DCS1 Pte. Ltd.HostingIPv4 IPv66
AS58057Securebit AGUnclassifiedIPv65
AS4913410VPN Research Network LTDUnclassifiedIPv41
AS212508Lowhosting services of Davide GennariUnclassifiedIPv41

Provenance

Where this comes from

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