bgpreport

Network · data from 2026-11-12

AS35833 mpex GmbH

Registry name: MPEXNET mpex GmbH, DE · PeeringDB

3IPv4 routes 0.0% RPKI valid · 66.7% with a route object
4IPv6 routes 0.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
7No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS35833, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS35833, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

81.17.218.0/24 No ROA Nonecovered by 81.17.216.0/21 669 99% 67
2a00:19c8::/36 No ROA Nonecovered by 2a00:19c8::/32 635 100% 69
2a00:19c8:8000::/36 No ROA Nonecovered by 2a00:19c8::/32 635 100% 69
81.17.208.0/20 No ROA RIR databaseRIPE 673 100% 66
81.17.216.0/21 No ROA RIR databaseRIPE 673 100% 66
2a00:19c8::/32 No ROA RIR databaseRIPE 636 100% 67
2a00:19c8::/29 No ROA RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS35833: AS-MPEXNETWORKS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS35833 isn't in the set, or no route object for AS35833 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS35833 in itNot covered
AS-MPEXNETWORKS RIPE 114 Yes 0

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 10 are in fix.csv.

  • ROA: none7
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: none81.17.218.0/24No ROA covers it. Add a ROA for AS35833, maxLength 24.669 of 673
Route object: none81.17.218.0/24No route object for it. A route object for 81.17.216.0/21 with origin AS35833 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35833 in the RIR database for the space.669 of 673
ROA: none2a00:19c8::/36No ROA covers it. Add a ROA for AS35833, maxLength 36.635 of 636
Route object: none2a00:19c8::/36No route object for it. A route object for 2a00:19c8::/32 with origin AS35833 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35833 in the RIR database for the space.635 of 636
ROA: none2a00:19c8:8000::/36No ROA covers it. Add a ROA for AS35833, maxLength 36.635 of 636
Route object: none2a00:19c8:8000::/36No route object for it. A route object for 2a00:19c8::/32 with origin AS35833 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35833 in the RIR database for the space.635 of 636
ROA: none81.17.208.0/20No ROA covers it. Add a ROA for AS35833, maxLength 20.673 of 673
ROA: none81.17.216.0/21No ROA covers it. Add a ROA for AS35833, maxLength 21.673 of 673
ROA: none2a00:19c8::/32No ROA covers it. Add a ROA for AS35833, maxLength 32.636 of 636
ROA: none2a00:19c8::/29No ROA covers it. Add a ROA for AS35833, maxLength 29.635 of 636

Route objects not announced

Every route object with origin AS35833 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.