Skip to main content

AS33838

BETANET-AS

BetaNET sp. z o.o.

Registry

Authoritative registration data

AS number
33838
Name
BETANET-AS
Organisation
BetaNET sp. z o.o.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS33838
83.142.152.0/21 IPv4 /21 not checked
193.138.136.0/22 IPv4 /22 not checked
194.150.100.0/22 IPv4 /22 not checked
193.16.99.0/24 IPv4 /24 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS33838 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS33838 in AS paths

Observed upstreams
Families
AS29535 334 1,059
v4
AS8308 129 441
v4
AS31242 59 292
v4
AS24115 ASN-EQIX-MLPE 8 30
v4
AS9141 AS9141 9 21
v4
AS137409 GSLNETWORKS-AS-AP 3 13
v4
AS6204 2 5
v4
AS35320 1 4
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS33838 in AS paths

Observed downstreams
Families
AS48047 258 342
v4

No rows match “”.

Showing of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 2 10
v4
AS24482 SGGS-AS-AP 2 5
v4
AS28917 2 5
v4
AS36236 NETACTUATE 2 5
v4

No rows match “”.

Showing of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.