Network · data from 2026-11-12
AS201687 MAM-JAHN
Registry name: MAM-JAHN Marco Andreas Martin Jahn, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS201687, 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.
| 2a02:2fc0:21::/48 | Invalid: origin | Other origin only | 24 4%low visibility |
| 2a09:3f00:3aff::/48 | No ROA | Nonecovered by 2a09:3f00:3a00::/40 | 635 100% |
| 2a09:3f00:3a00::/40 | No ROA | RIR databaseRIPE | 635 100% |
| 89.144.25.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.215.32.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.83.157.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a14:7c0:1200::/40 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS201687: RIPE::AS201687:AS-MAM-JAHN. 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 (AS201687 isn't in the set, or no route object for AS201687 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 | AS201687 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS201687:AS-MAM-JAHN | RIPE | 3 | 1 | 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 6 are in fix.csv.
- ROA: origin1
- ROA: none2
- Route object: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a02:2fc0:21::/48 | ROAs covering it name AS12586, not AS201687. If AS201687 should announce it, add a ROA for AS201687. |
| Route object: none | 2a02:2fc0:21::/48 | Route objects for it name AS12586. Add a route object with origin AS201687 in the RIR database for the space. |
| ROA: none | 2a09:3f00:3aff::/48 | No ROA covers it. Add a ROA for AS201687, maxLength 48. |
| Route object: none | 2a09:3f00:3aff::/48 | No route object for it. A route object for 2a09:3f00:3a00::/40 with origin AS201687 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201687 in the RIR database for the space. |
| ROA: none | 2a09:3f00:3a00::/40 | No ROA covers it. Add a ROA for AS201687, maxLength 40. |
Route objects not announced
Route objects with origin AS201687 whose prefix no peer sees AS201687 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:67c:6cc::/48 | RADB | 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.