Skip to main content

AS35833

MPEXNET

mpex GmbH

Registry

Authoritative registration data

AS number
35833
Name
MPEXNET
Organisation
mpex GmbH
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

4

Total announced

7

Announced prefixes

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

Prefixes announced by AS35833
81.17.208.0/20 IPv4 /20 not checked
81.17.216.0/21 IPv4 /21 not checked
81.17.218.0/24 IPv4 /24 not checked
2a00:19c8::/29 IPv6 /29 not checked
2a00:19c8::/32 IPv6 /32 not checked
2a00:19c8:8000::/36 IPv6 /36 not checked
2a00:19c8::/36 IPv6 /36 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS35833
Address families
BCIX: BCIX Peering LAN 20,000 Mbps IPv4 · IPv6

No rows match “”.

Showing of

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 AS35833 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS35833 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 295 858
v4 v6
AS13237 LAMBDANET-AS 188 685
v4 v6
AS3356 LEVEL3 229 622
v4 v6
AS9002 RETN-AS 27 90
v6
AS8218 NEO-ASN 6 85
v4 v6
AS39351 ESAB-AS 3 16
v4 v6
AS24961 2 14
v4 v6
AS6797 GLOBALCONNECT-NET 1 14
v4 v6
AS50629 LWLCOM 3 11
v4 v6
AS33891 CORE-BACKBONE 7 9
v4
AS20562 OPEN-PEERING-AS 3 6
v4 v6
AS15943 1 1
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS35833 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 49
v4 v6
AS680 DFN 1 6
v4 v6

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.