Network · data from 2026-11-12
AS48200 Opteamax GmbH
Registry name: OPTEAMAX-AS Opteamax GmbH, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48200, 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.
| 185.1.166.0/23 | Invalid: origin | Other origin only | 2 0%low visibility |
| 2a01:b1c0:10::/48 | Valid | Nonecovered by 2a01:b1c0::/32 | 2 0%low visibility |
| 84.39.104.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 84.39.111.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.36.46.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.62.23.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a01:b1c0::/32 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS48200: RIPE::AS48200:AS-OPTEAMAX. 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 (AS48200 isn't in the set, or no route object for AS48200 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.
| Name | Database | ASNs | Sets | AS48200 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS48200:AS-OPTEAMAX | RIPE1 member set in no database: AS-SDN-CLINIC-LAB | 209 | 32 | Yes | 1 |
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 8 are in fix.csv.
- ROA: origin1
- Route object: none2
- AS-SET: missing member1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 185.1.166.0/23 | ROAs covering it name AS202409, not AS48200. If AS48200 should announce it, add a ROA for AS48200. |
| Route object: none | 185.1.166.0/23 | Route objects for it name AS202409. Add a route object with origin AS48200 in the RIR database for the space. |
| Route object: none | 2a01:b1c0:10::/48 | No route object for it. A route object for 2a01:b1c0::/32 with origin AS48200 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48200 in the RIR database for the space. |
| AS-SET: missing member | RIPE::AS48200:AS-OPTEAMAX | AS48200:AS-OPTEAMAX (RIPE) lists AS-SDN-CLINIC-LAB; no IRR database read has it. |
Route objects not announced
Route objects with origin AS48200 whose prefix no peer sees AS48200 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 84.39.96.0/20 | RIPE | Valid |
| 84.39.96.0/21 | RIPE | Valid |
| 2a01:b1c0::/29 | RIPE | No ROA |
| 2a01:b1c0::/31 | RIPE | No ROA |
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.