Network · data from 2026-11-12
AS264987 AS264987 - RBR TELECOM SERVICOS DE TELEFONIA LIMITADA
Registry name: AS264987 - RBR TELECOM SERVICOS DE TELEFONIA LIMITADA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264987, 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:3104::/33 | Valid | Nonecovered by 2804:3104::/32 | 636 100% |
| 2804:3104::/34 | Valid | Nonecovered by 2804:3104::/32 | 636 100% |
| 2804:3104:4000::/34 | Valid | Nonecovered by 2804:3104::/32 | 635 100% |
| 2804:3104:8000::/33 | Valid | Nonecovered by 2804:3104::/32 | 635 100% |
| 2804:3104:8000::/34 | Valid | Nonecovered by 2804:3104::/32 | 635 100% |
| 2804:3104:c000::/34 | Valid | Nonecovered by 2804:3104::/32 | 635 100% |
| 45.224.2.0/24 | Valid | Nonecovered by 45.224.2.0/23 | 336 50% |
| 45.224.3.0/24 | Valid | Nonecovered by 45.224.2.0/23 | 336 50% |
| 170.84.12.0/23 | Valid | Nonecovered by 170.84.12.0/22 | 336 50% |
| 170.84.14.0/23 | Valid | Nonecovered by 170.84.12.0/22 | 336 50% |
| 181.191.56.0/23 | Valid | Nonecovered by 181.191.56.0/22 | 336 50% |
| 181.191.58.0/23 | Valid | Nonecovered by 181.191.56.0/22 | 336 50% |
| 181.191.56.0/24 | Valid | Nonecovered by 181.191.56.0/22 | 215 32% |
| 181.191.57.0/24 | Valid | Nonecovered by 181.191.56.0/22 | 215 32% |
| 181.191.58.0/24 | Valid | Nonecovered by 181.191.56.0/22 | 215 32% |
| 181.191.59.0/24 | Valid | Nonecovered by 181.191.56.0/22 | 215 32% |
| 170.84.12.0/24 | Valid | Nonecovered by 170.84.12.0/22 | 94 14% |
| 170.84.13.0/24 | Valid | Nonecovered by 170.84.12.0/22 | 94 14% |
| 170.84.14.0/24 | Valid | Nonecovered by 170.84.12.0/22 | 94 14% |
| 170.84.15.0/24 | Valid | Nonecovered by 170.84.12.0/22 | 94 14% |
| 45.224.2.0/23 | Valid | Other IRR onlyRADB | 670 100% |
| 170.84.12.0/22 | Valid | Other IRR onlyRADB | 670 100% |
| 181.191.56.0/22 | Valid | Other IRR onlyRADB | 670 100% |
| 2804:3104::/32 | Valid | Other IRR onlyRADB | 634 100% |
AS-SET
AS264987 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 24 are in fix.csv.
- Route object: none20
- Route object: RIR4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:3104::/33 | No route object for it. A route object for 2804:3104::/32 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: none | 2804:3104::/34 | No route object for it. A route object for 2804:3104::/32 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: none | 2804:3104:4000::/34 | No route object for it. A route object for 2804:3104::/32 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: none | 2804:3104:8000::/33 | No route object for it. A route object for 2804:3104::/32 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: none | 2804:3104:8000::/34 | No route object for it. A route object for 2804:3104::/32 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: none | 2804:3104:c000::/34 | No route object for it. A route object for 2804:3104::/32 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: none | 45.224.2.0/24 | No route object for it. A route object for 45.224.2.0/23 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: none | 45.224.3.0/24 | No route object for it. A route object for 45.224.2.0/23 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: none | 170.84.12.0/23 | No route object for it. A route object for 170.84.12.0/22 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: none | 170.84.14.0/23 | No route object for it. A route object for 170.84.12.0/22 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: none | 181.191.56.0/23 | No route object for it. A route object for 181.191.56.0/22 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: none | 181.191.58.0/23 | No route object for it. A route object for 181.191.56.0/22 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: none | 181.191.56.0/24 | No route object for it. A route object for 181.191.56.0/22 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: none | 181.191.57.0/24 | No route object for it. A route object for 181.191.56.0/22 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: none | 181.191.58.0/24 | No route object for it. A route object for 181.191.56.0/22 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: none | 181.191.59.0/24 | No route object for it. A route object for 181.191.56.0/22 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: none | 170.84.12.0/24 | No route object for it. A route object for 170.84.12.0/22 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: none | 170.84.13.0/24 | No route object for it. A route object for 170.84.12.0/22 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: none | 170.84.14.0/24 | No route object for it. A route object for 170.84.12.0/22 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: none | 170.84.15.0/24 | No route object for it. A route object for 170.84.12.0/22 with origin AS264987 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264987 in the RIR database for the space. |
| Route object: RIR | 45.224.2.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.84.12.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 181.191.56.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3104::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS264987 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.