asn.dev

Observed topology

AS36231 TEMPEST-HOSTING

Hosting RIPE

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

Transit

Upstream networks

All 14

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 IPv6908
AS6461Zayo BandwidthTransitIPv4 IPv6274
AS6939Hurricane Electric LLCTransitIPv4 IPv6222
AS1828Unitas GlobalUnclassifiedIPv4 IPv6219
AS61049Exascale LtdResidentialIPv4 IPv6162
AS50304Blix Solutions ASUnclassifiedIPv4 IPv636
AS24482SG.GSHostingIPv4 IPv618
AS48185team.blue NVUnclassifiedIPv4 IPv618
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv618
AS20764CJSC RASCOMUnclassifiedIPv411

All 14 upstreams →

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 IPv696
AS218703TEMPEST OPERATIONS UK LTDUnclassifiedIPv459
AS205848Dominik PohlHostingIPv636

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS396998Path Network, Inc.UnclassifiedIPv4 IPv6908
AS6461Zayo BandwidthTransitIPv4 IPv6343
AS6939Hurricane Electric LLCTransitIPv4 IPv6297
AS1828Unitas GlobalUnclassifiedIPv4 IPv6219
AS61049Exascale LtdResidentialIPv4 IPv6195
AS210667Adam GoodenoughHostingIPv4 IPv696
AS218703TEMPEST OPERATIONS UK LTDUnclassifiedIPv459
AS50304Blix Solutions ASUnclassifiedIPv4 IPv638
AS205848Dominik PohlHostingIPv636
AS24482SG.GSHostingIPv4 IPv622

All 17 adjacent →

Provenance

Where this comes from

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