asn.dev

Observed topology

AS48925 VIBEGAMES

Hosting RIPE Content

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS48925: 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
AS60068Datacamp LimitedHostingIPv41,983
AS1136KPN B.V.ResidentialIPv435
AS34927iFog GmbHHostingIPv435
AS202365Omer GOLGELIUnclassifiedIPv435
AS401753BIXCE IncUnclassifiedIPv435
AS43278Castles LLCUnclassifiedIPv433
AS20764CJSC RASCOMUnclassifiedIPv42
AS197195VibeGAMES B.V.UnclassifiedIPv41

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS214987VibeGAMES B.V.UnclassifiedIPv4480
AS197195VibeGAMES B.V.UnclassifiedIPv460
AS213606Jose Luis Monserrat AlburquenqueUnclassifiedIPv460
AS214034KirieLABS CommVUnclassifiedIPv458

Adjacency

Adjacent networks

All 19

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

ASNetworkTypeFamiliesPaths seen
AS60068Datacamp LimitedHostingIPv42,517
AS214987VibeGAMES B.V.UnclassifiedIPv4480
AS197195VibeGAMES B.V.UnclassifiedIPv461
AS213606Jose Luis Monserrat AlburquenqueUnclassifiedIPv460
AS174Cogent Communications, LLCTransitIPv459
AS214034KirieLABS CommVUnclassifiedIPv458
AS34927iFog GmbHHostingIPv445
AS401753BIXCE IncUnclassifiedIPv445
AS202365Omer GOLGELIUnclassifiedIPv444
AS43278Castles LLCUnclassifiedIPv442

All 19 adjacent →

Provenance

Where this comes from

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