asn.dev

Observed topology

AS200799 AS-SILTEL Internet Service Provider

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS200799: 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
AS44092HAL Service SpAResidentialIPv4247
AS174Cogent Communications, LLCTransitIPv4234
AS6939Hurricane Electric LLCTransitIPv4131
AS3302Retelit Digital Services S.p.A.UnclassifiedIPv442
AS24482SG.GSHostingIPv412
AS31543myNet GmbHResidentialIPv412
AS59919Brainbox S.r.l.ResidentialIPv412
AS8218Zayo Infrastructure France SAUnclassifiedIPv48

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS51872SILTEL TELECOMUNICAZIONI SRLUnclassifiedIPv4115
AS206380SILTEL TELECOMUNICAZIONI SRLUnclassifiedIPv458
AS212394ISS S.R.L.S.UnclassifiedIPv411

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS44092HAL Service SpAResidentialIPv4331
AS174Cogent Communications, LLCTransitIPv4286
AS6939Hurricane Electric LLCTransitIPv4161
AS51872SILTEL TELECOMUNICAZIONI SRLUnclassifiedIPv4115
AS206380SILTEL TELECOMUNICAZIONI SRLUnclassifiedIPv458
AS3302Retelit Digital Services S.p.A.UnclassifiedIPv451
AS24482SG.GSHostingIPv415
AS31543myNet GmbHResidentialIPv415
AS59919Brainbox S.r.l.ResidentialIPv415
AS212394ISS S.R.L.S.UnclassifiedIPv411

All 11 adjacent →

Provenance

Where this comes from

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