Network · data from 2026-11-12
AS39567 MD6 Consulting
Registry name: MD6-FR OCI Cloud SAS, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS39567, 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.65.28.0/22 | No ROA | Other origin only | 673 100% |
| 185.231.120.0/22 | No ROA | Other origin only | 673 100% |
| 185.231.120.0/23 | No ROA | None | 673 100% |
| 185.231.122.0/23 | No ROA | None | 673 100% |
| 2a03:18e0::/32 | No ROA | None | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS39567: RIPE::AS-MD6. 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 (AS39567 isn't in the set, or no route object for AS39567 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 | AS39567 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-MD6 | RIPE | 1 | 1 | Yes | 5 |
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: none5
- Route object: none5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.65.28.0/22 | No ROA covers it. Add a ROA for AS39567, maxLength 22. |
| Route object: none | 185.65.28.0/22 | Route objects for it name AS61136. Add a route object with origin AS39567 in the RIR database for the space. |
| ROA: none | 185.231.120.0/22 | No ROA covers it. Add a ROA for AS39567, maxLength 22. |
| Route object: none | 185.231.120.0/22 | Route objects for it name AS61136. Add a route object with origin AS39567 in the RIR database for the space. |
| ROA: none | 185.231.120.0/23 | No ROA covers it. Add a ROA for AS39567, maxLength 23. |
| Route object: none | 185.231.120.0/23 | No route object for it. Add a route object with origin AS39567 in the RIR database for the space. |
| ROA: none | 185.231.122.0/23 | No ROA covers it. Add a ROA for AS39567, maxLength 23. |
| Route object: none | 185.231.122.0/23 | No route object for it. Add a route object with origin AS39567 in the RIR database for the space. |
| ROA: none | 2a03:18e0::/32 | No ROA covers it. Add a ROA for AS39567, maxLength 32. |
| Route object: none | 2a03:18e0::/32 | No route object for it. Add a route object with origin AS39567 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS39567 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.