Network · data from 2026-11-12
AS62387 datafabrik.de
Registry name: MEERFARBIG-AS meerfarbig GmbH & Co. KG, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS62387, 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.
| 79.132.64.0/19 | No ROA | None | 673 100% |
| 79.135.136.0/22 | No ROA | None | 673 100% |
| 123.98.36.0/22 | No ROA | None | 2 0%low visibility |
| 88.223.208.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 45.13.148.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 79.132.176.0/20 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS62387: AS-DATAFABRIK. 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 (AS62387 isn't in the set, or no route object for AS62387 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 | AS62387 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-DATAFABRIK | In no IRR database read today. | |||||
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 9 are in fix.csv.
- ROA: none4
- Route object: none3
- AS-SET: not found1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 79.132.64.0/19 | No ROA covers it. Add a ROA for AS62387, maxLength 19. |
| Route object: none | 79.132.64.0/19 | No route object for it. Add a route object with origin AS62387 in the RIR database for the space. |
| ROA: none | 79.135.136.0/22 | No ROA covers it. Add a ROA for AS62387, maxLength 22. |
| Route object: none | 79.135.136.0/22 | No route object for it. Add a route object with origin AS62387 in the RIR database for the space. |
| ROA: none | 123.98.36.0/22 | No ROA covers it. Add a ROA for AS62387, maxLength 22. |
| Route object: none | 123.98.36.0/22 | No route object for it. Add a route object with origin AS62387 in the RIR database for the space. |
| ROA: none | 88.223.208.0/20 | No ROA covers it. Add a ROA for AS62387, maxLength 20. |
| AS-SET: not found | AS-DATAFABRIK | PeeringDB names AS-DATAFABRIK; no IRR database read has it. |
Route objects not announced
Route objects with origin AS62387 whose prefix no peer sees AS62387 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 79.132.92.0/22 | RIPE | Valid |
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.