Network · data from 2026-11-12
AS267459 R3TELECOM INTERNET
Registry name: AS267459 - R3TELECOM INTERNET, BR · PeeringDB
5IPv4 routes
100.0% RPKI valid · 100.0% with a route object
11IPv6 routes
100.0% RPKI valid · 45.5% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
6 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
5Route objects not announced
registered with origin AS267459, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS267459, 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:41d4::/48 | Valid | Nonecovered by 2804:41d4::/34 | 634 100% |
| 2804:41d4:50::/44 | Valid | Nonecovered by 2804:41d4::/34 | 634 100% |
| 2804:41d4:fc00::/48 | Valid | Nonecovered by 2804:41d4:c000::/34 | 634 100% |
| 2804:41d4:fc02::/48 | Valid | Nonecovered by 2804:41d4:c000::/34 | 634 100% |
| 2804:41d4:40::/44 | Valid | Nonecovered by 2804:41d4::/34 | 632 99% |
| 2804:41d4:fc01::/48 | Valid | Nonecovered by 2804:41d4:c000::/34 | 632 99% |
| 192.141.88.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 192.141.89.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 192.141.88.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 192.141.90.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 192.141.91.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 2804:41d4::/34 | Valid | Other IRR onlyTC | 634 100% |
| 2804:41d4:4000::/34 | Valid | Other IRR onlyTC | 634 100% |
| 2804:41d4:8000::/34 | Valid | Other IRR onlyTC | 634 100% |
| 2804:41d4:c000::/34 | Valid | Other IRR onlyTC | 634 100% |
| 2804:41d4::/32 | Valid | Other IRR onlyRADB, TC | 632 99% |
AS-SET
AS267459'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 21 are in fix.csv.
- Route object: none6
- Route object: RIR10
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:41d4::/48 | No route object for it. A route object for 2804:41d4::/34 with origin AS267459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267459 in the RIR database for the space. |
| Route object: none | 2804:41d4:50::/44 | No route object for it. A route object for 2804:41d4::/34 with origin AS267459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267459 in the RIR database for the space. |
| Route object: none | 2804:41d4:fc00::/48 | No route object for it. A route object for 2804:41d4:c000::/34 with origin AS267459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267459 in the RIR database for the space. |
| Route object: none | 2804:41d4:fc02::/48 | No route object for it. A route object for 2804:41d4:c000::/34 with origin AS267459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267459 in the RIR database for the space. |
| Route object: none | 2804:41d4:40::/44 | No route object for it. A route object for 2804:41d4::/34 with origin AS267459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267459 in the RIR database for the space. |
| Route object: none | 2804:41d4:fc01::/48 | No route object for it. A route object for 2804:41d4:c000::/34 with origin AS267459 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267459 in the RIR database for the space. |
| Route object: RIR | 192.141.88.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 192.141.89.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 192.141.88.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 192.141.90.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 192.141.91.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:41d4::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:41d4:4000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:41d4:8000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:41d4:c000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:41d4::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267459 whose prefix no peer sees AS267459 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.141.88.0/23 | TC | Valid |
| 192.141.90.0/23 | TC | Valid |
| 2804:41d4::/33 | TC | Valid |
| 2804:41d4:fff::/48 | RADB | Valid |
| 2804:41d4:8000::/33 | TC | Valid |
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.