asn.dev

Observed topology

AS48096 ITGRAD Enterprise Cloud Ltd.

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48096: 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
AS8359MTS PJSCMobileIPv43,306
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv62,695
AS200590NLS Kazakhstan LLCUnclassifiedIPv4 IPv6719
AS57681PJSC Moscow city telephone networkUnclassifiedIPv4629
AS41798JSC TranstelecomUnclassifiedIPv4128
AS20764CJSC RASCOMUnclassifiedIPv4 IPv670
AS9002RETN LimitedUnclassifiedIPv4 IPv614

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS212189IT-GRAD TOOUnclassifiedIPv4996
AS51593Quasar Limited Liability CompanyUnclassifiedIPv421

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS8359MTS PJSCMobileIPv43,306
AS57304JSC "RetnNet"UnclassifiedIPv4 IPv62,713
AS200590NLS Kazakhstan LLCUnclassifiedIPv4 IPv61,395
AS212189IT-GRAD TOOUnclassifiedIPv4996
AS57681PJSC Moscow city telephone networkUnclassifiedIPv4632
AS41798JSC TranstelecomUnclassifiedIPv4448
AS20764CJSC RASCOMUnclassifiedIPv4 IPv670
AS51593Quasar Limited Liability CompanyUnclassifiedIPv421
AS9002RETN LimitedUnclassifiedIPv4 IPv614

Provenance

Where this comes from

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