asn.dev

Observed topology

AS36231 Tempest-Hosting AGX Management Consultancy - FZCO

Hosting RIPE Content

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

Transit

Upstream networks

All 15

Networks observed carrying traffic for AS36231: 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
AS396998Path Network, Inc.UnclassifiedIPv4 IPv6716
AS3257GTT Communications Inc.TransitIPv4 IPv6335
AS6461Zayo BandwidthTransitIPv4 IPv6252
AS6939Hurricane Electric LLCTransitIPv4 IPv6243
AS1828Unitas GlobalUnclassifiedIPv4 IPv6223
AS61049Exascale LtdResidentialIPv4 IPv6197
AS50304Blix Solutions ASUnclassifiedIPv4 IPv642
AS24482SG.GSHostingIPv4 IPv627
AS48185team.blue NVUnclassifiedIPv4 IPv621
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv621

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS210667Adam GoodenoughHostingIPv4 IPv695
AS218703TEMPEST OPERATIONS UK LTDUnclassifiedIPv459
AS205848Dominik PohlHostingIPv635

Adjacency

Adjacent networks

All 18

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

ASNetworkTypeFamiliesPaths seen
AS396998Path Network, Inc.UnclassifiedIPv4 IPv6716
AS3257GTT Communications Inc.TransitIPv4 IPv6335
AS6939Hurricane Electric LLCTransitIPv4 IPv6320
AS6461Zayo BandwidthTransitIPv4 IPv6317
AS61049Exascale LtdResidentialIPv4 IPv6230
AS1828Unitas GlobalUnclassifiedIPv4 IPv6223
AS210667Adam GoodenoughHostingIPv4 IPv695
AS218703TEMPEST OPERATIONS UK LTDUnclassifiedIPv459
AS50304Blix Solutions ASUnclassifiedIPv4 IPv644
AS205848Dominik PohlHostingIPv635

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.