asn.dev

Observed topology

AS136258 ONEPROVIDER-AS - BrainStorm Network, Inc

Unclassified APNIC Enterprise

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

Transit

Upstream networks

All 34

Networks observed carrying traffic for AS136258: 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
AS396356Latitude.shHostingIPv4 IPv61,832
AS46475Limestone Networks, Inc.HostingIPv4 IPv6444
AS36352HostPapaHostingIPv4 IPv6414
AS262287Latitude.sh LTDAHostingIPv4 IPv6384
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv6325
AS62563GLOBALTELEHOST Corp.HostingIPv4 IPv6299
AS63023GTHostHostingIPv4 IPv6295
AS55720Gigabit Hosting Sdn BhdHostingIPv4 IPv6247
AS56655Gigahost ASUnclassifiedIPv4 IPv6232
AS49367Seflow s.r.l.HostingIPv4 IPv6212

All 34 upstreams →

Transit

Downstream networks

inferred

Networks for which AS136258 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 34

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

ASNetworkTypeFamiliesPaths seen
AS396356Latitude.shHostingIPv4 IPv61,832
AS46475Limestone Networks, Inc.HostingIPv4 IPv6444
AS36352HostPapaHostingIPv4 IPv6414
AS262287Latitude.sh LTDAHostingIPv4 IPv6384
AS7195EDGEUNO S.A.SUnclassifiedIPv4 IPv6325
AS62563GLOBALTELEHOST Corp.HostingIPv4 IPv6299
AS63023GTHostHostingIPv4 IPv6295
AS55720Gigabit Hosting Sdn BhdHostingIPv4 IPv6247
AS56655Gigahost ASUnclassifiedIPv4 IPv6232
AS146943Tier 4 Cloud ServicesHostingIPv4 IPv6213

All 34 adjacent →

Provenance

Where this comes from

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