asn.dev

Observed topology

AS59815 TRINITY-AS Trinity Ltd

Unclassified RIPE

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

Transit

Upstream networks

All 11

Networks observed carrying traffic for AS59815: 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
AS201776Miranda-Media LtdUnclassifiedIPv4616
AS206810GUP DNR "UGLETELECOM"UnclassifiedIPv4226
AS52091Level-MSK Ltd.UnclassifiedIPv448
AS50673Serverius Holding B.V.UnclassifiedIPv429
AS6939Hurricane Electric LLCTransitIPv424
AS24482SG.GSHostingIPv416
AS37721Virtual Technologies & SolutionsResidentialIPv416
AS49673Truenetwork LLCUnclassifiedIPv416
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv416
AS8447A1 Telekom Austria AGResidentialIPv45

All 11 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS25299Trinity LtdUnclassifiedIPv4633

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS201776Miranda-Media LtdUnclassifiedIPv4819
AS25299Trinity LtdUnclassifiedIPv4633
AS206810GUP DNR "UGLETELECOM"UnclassifiedIPv4340
AS52091Level-MSK Ltd.UnclassifiedIPv4260
AS6939Hurricane Electric LLCTransitIPv466
AS50673Serverius Holding B.V.UnclassifiedIPv444
AS24482SG.GSHostingIPv426
AS37721Virtual Technologies & SolutionsResidentialIPv426
AS49673Truenetwork LLCUnclassifiedIPv426
AS208972GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETIUnclassifiedIPv426

All 12 adjacent →

Provenance

Where this comes from

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