asn.dev

Observed topology

AS207249 ICS Icard Services PLC

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS207249: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6188
AS9008Visual Online S.A.ResidentialIPv4 IPv6130
AS34224Neterra Ltd.UnclassifiedIPv458
AS3223Voxility LLPHostingIPv432
AS8220COLT Technology Services Group LimitedHostingIPv4 IPv621
AS3356Level 3 Parent, LLCTransitIPv416

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS47557Icard Services PLCUnclassifiedIPv4 IPv6228
AS59872Icard Services PLCUnclassifiedIPv636
AS197741Icard Services PLCUnclassifiedIPv47

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6403
AS47557Icard Services PLCUnclassifiedIPv4 IPv6228
AS9008Visual Online S.A.ResidentialIPv4 IPv6130
AS34224Neterra Ltd.UnclassifiedIPv465
AS8220COLT Technology Services Group LimitedHostingIPv4 IPv655
AS59872Icard Services PLCUnclassifiedIPv636
AS3223Voxility LLPHostingIPv432
AS3356Level 3 Parent, LLCTransitIPv431
AS197741Icard Services PLCUnclassifiedIPv47

Provenance

Where this comes from

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