Observed topology

AS33838 BETANET-AS BetaNET sp. z o.o.

Unclassified RIPE

Upstreams 6 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 7

Adjacent (IPv6) 0

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

Transit

Upstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS29535	Orange Polska Spolka Akcyjna	Unclassified	IPv4	176
AS31242	P4 Sp. z o.o.	Mobile	IPv4	68
AS9141	P4 Sp. z o.o.	Mobile	IPv4	8
AS5617	Orange Polska Spolka Akcyjna	Mobile	IPv4	4
AS24115	Equinix	Hosting	IPv4	4
AS24482	SG.GS	Hosting	IPv4	4

Transit

Downstream networks

inferred

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

AS	Network	Type	Families	Paths seen
AS48047	Lukasz Chrustek Krakowskie Centrum Przetwarzania Danych	Unclassified	IPv4	54

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS29535	Orange Polska Spolka Akcyjna	Unclassified	IPv4	226
AS31242	P4 Sp. z o.o.	Mobile	IPv4	68
AS48047	Lukasz Chrustek Krakowskie Centrum Przetwarzania Danych	Unclassified	IPv4	54
AS9141	P4 Sp. z o.o.	Mobile	IPv4	10
AS5617	Orange Polska Spolka Akcyjna	Mobile	IPv4	5
AS24482	SG.GS	Hosting	IPv4	5
AS24115	Equinix	Hosting	IPv4	4

Provenance

Where this comes from

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