asn.dev

Observed topology

AS44628 UAPROSTIR

Unclassified RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS44628: 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
AS35297Dataline LLCUnclassifiedIPv4459
AS6768"EUROTELE-PLUS" LLCUnclassifiedIPv480
AS9002RETN LimitedUnclassifiedIPv473
AS3326PRIVATE JOINT STOCK COMPANY "DATAGROUP"ResidentialIPv428
AS24482SG.GSHostingIPv410

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS3266UAB PorentaUnclassifiedIPv4260
AS48696FOP Oleh Igorovich LumerUnclassifiedIPv459
AS48674UAProstir Ltd.UnclassifiedIPv427

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS35297Dataline LLCUnclassifiedIPv4513
AS6768"EUROTELE-PLUS" LLCUnclassifiedIPv4264
AS3266UAB PorentaUnclassifiedIPv4260
AS9002RETN LimitedUnclassifiedIPv4125
AS3326PRIVATE JOINT STOCK COMPANY "DATAGROUP"ResidentialIPv480
AS48696FOP Oleh Igorovich LumerUnclassifiedIPv459
AS48674UAProstir Ltd.UnclassifiedIPv427
AS24482SG.GSHostingIPv414

Provenance

Where this comes from

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