Network · data from 2026-11-12
AS270500 AS270500 - F & L SERVICOS E TELECOMUNICACOES EIRELI
Registry name: AS270500 - F & L SERVICOS E TELECOMUNICACOES EIRELI, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270500, 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.
| 189.85.99.0/24 | No ROA | Nonecovered by 189.85.96.0/22 | 670 100% |
| 189.85.96.0/24 | No ROA | Nonecovered by 189.85.96.0/22 | 669 99% |
| 189.85.98.0/23 | No ROA | Nonecovered by 189.85.96.0/22 | 669 99% |
| 189.85.98.0/24 | No ROA | Nonecovered by 189.85.96.0/22 | 669 99% |
| 189.85.97.0/24 | No ROA | Nonecovered by 189.85.96.0/22 | 664 99% |
| 2804:6ce8::/33 | No ROA | Nonecovered by 2804:6ce8::/32 | 636 100% |
| 2804:6ce8:8000::/36 | No ROA | Nonecovered by 2804:6ce8::/32 | 635 100% |
AS-SET
AS270500 isn't in PeeringDB, where networks name their 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: none7
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 189.85.99.0/24 | No ROA covers it. Add a ROA for AS270500, maxLength 24. |
| Route object: none | 189.85.99.0/24 | No route object for it. A route object for 189.85.96.0/22 with origin AS270500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270500 in the RIR database for the space. |
| ROA: none | 189.85.96.0/24 | No ROA covers it. Add a ROA for AS270500, maxLength 24. |
| Route object: none | 189.85.96.0/24 | No route object for it. A route object for 189.85.96.0/22 with origin AS270500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270500 in the RIR database for the space. |
| ROA: none | 189.85.98.0/23 | No ROA covers it. Add a ROA for AS270500, maxLength 23. |
| Route object: none | 189.85.98.0/23 | No route object for it. A route object for 189.85.96.0/22 with origin AS270500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270500 in the RIR database for the space. |
| ROA: none | 189.85.98.0/24 | No ROA covers it. Add a ROA for AS270500, maxLength 24. |
| Route object: none | 189.85.98.0/24 | No route object for it. A route object for 189.85.96.0/22 with origin AS270500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270500 in the RIR database for the space. |
| ROA: none | 189.85.97.0/24 | No ROA covers it. Add a ROA for AS270500, maxLength 24. |
| Route object: none | 189.85.97.0/24 | No route object for it. A route object for 189.85.96.0/22 with origin AS270500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270500 in the RIR database for the space. |
| ROA: none | 2804:6ce8::/33 | No ROA covers it. Add a ROA for AS270500, maxLength 33. |
| Route object: none | 2804:6ce8::/33 | No route object for it. A route object for 2804:6ce8::/32 with origin AS270500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270500 in the RIR database for the space. |
| ROA: none | 2804:6ce8:8000::/36 | No ROA covers it. Add a ROA for AS270500, maxLength 36. |
| Route object: none | 2804:6ce8:8000::/36 | No route object for it. A route object for 2804:6ce8::/32 with origin AS270500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270500 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS270500 whose prefix no peer sees AS270500 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 189.85.96.0/22 | ALTDB, RADB | No ROA |
| 2804:6ce8::/32 | ALTDB, 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.