Network · data from 2026-11-12
AS271185 BRTELE TECNOLOGIA
Registry name: AS271185 - BRTELE TECNOLOGIA LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS271185, 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.
| 190.5.208.0/23 | Valid | Nonecovered by 190.5.208.0/22 | 671 100% |
| 190.5.210.0/23 | Valid | Nonecovered by 190.5.208.0/22 | 671 100% |
| 2804:778c::/33 | Valid | Nonecovered by 2804:778c::/32 | 633 100% |
| 190.5.209.0/24 | Valid | Nonecovered by 190.5.208.0/22 | 11 2%low visibility |
| 190.5.208.0/24 | Valid | Nonecovered by 190.5.208.0/22 | 9 1%low visibility |
| 190.5.210.0/24 | Valid | Nonecovered by 190.5.208.0/22 | 9 1%low visibility |
| 190.5.211.0/24 | Valid | Nonecovered by 190.5.208.0/22 | 9 1%low visibility |
| 190.5.208.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 2804:778c::/32 | Valid | Other IRR onlyRADB, TC | 633 100% |
AS-SET
AS271185'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 9 are in fix.csv.
- Route object: none7
- Route object: RIR2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 190.5.208.0/23 | No route object for it. A route object for 190.5.208.0/22 with origin AS271185 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271185 in the RIR database for the space. |
| Route object: none | 190.5.210.0/23 | No route object for it. A route object for 190.5.208.0/22 with origin AS271185 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271185 in the RIR database for the space. |
| Route object: none | 2804:778c::/33 | No route object for it. A route object for 2804:778c::/32 with origin AS271185 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271185 in the RIR database for the space. |
| Route object: none | 190.5.209.0/24 | No route object for it. A route object for 190.5.208.0/22 with origin AS271185 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271185 in the RIR database for the space. |
| Route object: none | 190.5.208.0/24 | No route object for it. A route object for 190.5.208.0/22 with origin AS271185 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271185 in the RIR database for the space. |
| Route object: none | 190.5.210.0/24 | No route object for it. A route object for 190.5.208.0/22 with origin AS271185 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271185 in the RIR database for the space. |
| Route object: none | 190.5.211.0/24 | No route object for it. A route object for 190.5.208.0/22 with origin AS271185 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271185 in the RIR database for the space. |
| Route object: RIR | 190.5.208.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:778c::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS271185 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.