asn.dev

Observed topology

AS36902 Intelvision Ltd - Intelvision Ltd

Residential AFRINIC Cable/DSL/ISP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS36902: 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
AS23764CTGNetUnclassifiedIPv41,504
AS30844Liquid Telecommunications LtdUnclassifiedIPv4374
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv4335
AS6939Hurricane Electric LLCTransitIPv4278
AS37721Virtual Technologies & SolutionsResidentialIPv434

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS36867Kokonet LtdUnclassifiedIPv4732
AS327861Department of ICT Government of SeychellesUnclassifiedIPv412

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS23764CTGNetUnclassifiedIPv42,027
AS36867Kokonet LtdUnclassifiedIPv4732
AS37662West Indian Ocean Cable CompanyUnclassifiedIPv4421
AS30844Liquid Telecommunications LtdUnclassifiedIPv4413
AS6939Hurricane Electric LLCTransitIPv4362
AS37721Virtual Technologies & SolutionsResidentialIPv446
AS327861Department of ICT Government of SeychellesUnclassifiedIPv412

Provenance

Where this comes from

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