Network · data from 2026-11-12
AS266646 MEYER TELECOM
Registry name: AS266646 - MEYER TELECOM, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS266646, 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.
| 2804:3f38::/36 | No ROA | Nonecovered by 2804:3f38::/32 | 16 3%low visibility |
| 2804:3f38:1000::/36 | No ROA | Nonecovered by 2804:3f38::/32 | 16 3%low visibility |
| 2804:3f38:9000::/36 | No ROA | Nonecovered by 2804:3f38::/32 | 16 3%low visibility |
| 128.201.96.0/24 | No ROA | Nonecovered by 128.201.96.0/23 | 1 0%low visibility |
| 128.201.97.0/24 | No ROA | Nonecovered by 128.201.96.0/23 | 1 0%low visibility |
| 128.201.96.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 128.201.98.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 128.201.99.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
AS-SET
AS266646's PeeringDB record names no AS-SET.
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 18 are in fix.csv.
- ROA: none8
- Route object: none5
- Route object: RIR3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:3f38::/36 | No ROA covers it. Add a ROA for AS266646, maxLength 36. |
| Route object: none | 2804:3f38::/36 | No route object for it. A route object for 2804:3f38::/32 with origin AS266646 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266646 in the RIR database for the space. |
| ROA: none | 2804:3f38:1000::/36 | No ROA covers it. Add a ROA for AS266646, maxLength 36. |
| Route object: none | 2804:3f38:1000::/36 | No route object for it. A route object for 2804:3f38::/32 with origin AS266646 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266646 in the RIR database for the space. |
| ROA: none | 2804:3f38:9000::/36 | No ROA covers it. Add a ROA for AS266646, maxLength 36. |
| Route object: none | 2804:3f38:9000::/36 | No route object for it. A route object for 2804:3f38::/32 with origin AS266646 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266646 in the RIR database for the space. |
| ROA: none | 128.201.96.0/24 | No ROA covers it. Add a ROA for AS266646, maxLength 24. |
| Route object: none | 128.201.96.0/24 | No route object for it. A route object for 128.201.96.0/23 with origin AS266646 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266646 in the RIR database for the space. |
| ROA: none | 128.201.97.0/24 | No ROA covers it. Add a ROA for AS266646, maxLength 24. |
| Route object: none | 128.201.97.0/24 | No route object for it. A route object for 128.201.96.0/23 with origin AS266646 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266646 in the RIR database for the space. |
| ROA: none | 128.201.96.0/23 | No ROA covers it. Add a ROA for AS266646, maxLength 23. |
| Route object: RIR | 128.201.96.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 128.201.98.0/24 | No ROA covers it. Add a ROA for AS266646, maxLength 24. |
| Route object: RIR | 128.201.98.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 128.201.99.0/24 | No ROA covers it. Add a ROA for AS266646, maxLength 24. |
| Route object: RIR | 128.201.99.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS266646 whose prefix no peer sees AS266646 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 128.201.96.0/22 | RADB, TC | No ROA |
| 2804:3f38::/32 | RADB, TC | 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.