Network · data from 2026-11-12
AS264063 IMA TELECOM
Registry name: AS264063 - IMA TELECOM LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264063, 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.
| 143.137.49.0/24 | No ROA | Nonecovered by 143.137.48.0/23 | 670 100% |
| 143.137.50.0/24 | No ROA | Nonecovered by 143.137.50.0/23 | 670 100% |
| 143.137.51.0/24 | No ROA | Nonecovered by 143.137.50.0/23 | 670 100% |
| 143.137.48.0/24 | No ROA | Nonecovered by 143.137.48.0/23 | 669 99% |
| 2804:2a30:8::/45 | No ROA | Nonecovered by 2804:2a30::/32 | 635 100% |
| 143.137.48.0/22 | No ROA | Other IRR onlyRADB, TC | 670 100% |
| 2804:2a30::/32 | No ROA | Other IRR onlyRADB, TC | 635 100% |
AS-SET
AS264063'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 16 are in fix.csv.
- ROA: none7
- Route object: none5
- Route object: RIR2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 143.137.49.0/24 | No ROA covers it. Add a ROA for AS264063, maxLength 24. |
| Route object: none | 143.137.49.0/24 | No route object for it. A route object for 143.137.48.0/23 with origin AS264063 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264063 in the RIR database for the space. |
| ROA: none | 143.137.50.0/24 | No ROA covers it. Add a ROA for AS264063, maxLength 24. |
| Route object: none | 143.137.50.0/24 | No route object for it. A route object for 143.137.50.0/23 with origin AS264063 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264063 in the RIR database for the space. |
| ROA: none | 143.137.51.0/24 | No ROA covers it. Add a ROA for AS264063, maxLength 24. |
| Route object: none | 143.137.51.0/24 | No route object for it. A route object for 143.137.50.0/23 with origin AS264063 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264063 in the RIR database for the space. |
| ROA: none | 143.137.48.0/24 | No ROA covers it. Add a ROA for AS264063, maxLength 24. |
| Route object: none | 143.137.48.0/24 | No route object for it. A route object for 143.137.48.0/23 with origin AS264063 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264063 in the RIR database for the space. |
| ROA: none | 2804:2a30:8::/45 | No ROA covers it. Add a ROA for AS264063, maxLength 45. |
| Route object: none | 2804:2a30:8::/45 | No route object for it. A route object for 2804:2a30::/32 with origin AS264063 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264063 in the RIR database for the space. |
| ROA: none | 143.137.48.0/22 | No ROA covers it. Add a ROA for AS264063, maxLength 22. |
| Route object: RIR | 143.137.48.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:2a30::/32 | No ROA covers it. Add a ROA for AS264063, maxLength 32. |
| Route object: RIR | 2804:2a30::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS264063 whose prefix no peer sees AS264063 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 143.137.48.0/23 | RADB | No ROA |
| 143.137.50.0/23 | 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.