asn.dev

Observed topology

AS198890 MADCOM-ASN

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS198890: 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
AS174Cogent Communications, LLCTransitIPv490
AS6939Hurricane Electric LLCTransitIPv4 IPv658
AS3257GTT Communications Inc.TransitIPv4 IPv648
AS24482SG.GSHostingIPv43
AS31543myNet GmbHResidentialIPv43
AS59919Brainbox S.r.l.ResidentialIPv43

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS209240ISA.NET Sh.p.k.UnclassifiedIPv4186
AS33924Pronet sh.p.k.ResidentialIPv4 IPv6149
AS213683Host.AL ShpkHostingIPv4102
AS48265NSolution sh.p.kUnclassifiedIPv470
AS213612OTP Bank Albania Sh.A.UnclassifiedIPv457
AS60471Mobitel sh.p.k.UnclassifiedIPv425
AS197706Keminet SHPKUnclassifiedIPv616
AS215910Edma Net SHPKUnclassifiedIPv42

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS174Cogent Communications, LLCTransitIPv4 IPv6456
AS3257GTT Communications Inc.TransitIPv4 IPv6227
AS209240ISA.NET Sh.p.k.UnclassifiedIPv4186
AS33924Pronet sh.p.k.ResidentialIPv4 IPv6149
AS213683Host.AL ShpkHostingIPv4126
AS6939Hurricane Electric LLCTransitIPv4 IPv699
AS48265NSolution sh.p.kUnclassifiedIPv470
AS213612OTP Bank Albania Sh.A.UnclassifiedIPv457
AS197706Keminet SHPKUnclassifiedIPv653
AS24482SG.GSHostingIPv431

Provenance

Where this comes from

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