Observed topology

AS154809 GLOBEX TRADING CO. LIMITED

Unclassified APNIC

Upstreams 0 carry this network

Downstreams 0 this network carries

Adjacent (IPv4) 13

Adjacent (IPv6) 0

Upstream graph Who carries AS154809, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS154809 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS154809: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 13

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

AS	Network	Type	Families	Paths seen
AS49666	Telecommunication Infrastructure Company	Unclassified	IPv4	5,487
AS57463	NetIX Communications JSC	Unclassified	IPv4	2,802
AS31490	NetIX Communications JSC	Unclassified	IPv4	621
AS34927	iFog GmbH	Hosting	IPv4	332
AS50673	Serverius Holding B.V.	Unclassified	IPv4	332
AS206499	LOCIX LIMITED	Unclassified	IPv4	330
AS24482	SG.GS	Hosting	IPv4	297
AS34549	meerfarbig GmbH & Co. KG	Hosting	IPv4	274
AS37721	Virtual Technologies & Solutions	Residential	IPv4	251
AS58057	Securebit AG	Unclassified	IPv4	96

All 13 adjacent →

Provenance

Where this comes from

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