Network · data from 2026-11-12
AS262436 Futuro Telecom Ltda
Registry name: AS262436 - FUTURO TELECOM LTDA, BR · PeeringDB
14IPv4 routes
100.0% RPKI valid · 14.3% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
12 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS262436, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS262436, 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.
| 177.52.32.0/24 | Valid | Nonecovered by 177.52.32.0/22 | 168 25% |
| 177.52.33.0/24 | Valid | Nonecovered by 177.52.32.0/22 | 168 25% |
| 177.52.34.0/24 | Valid | Nonecovered by 177.52.32.0/22 | 168 25% |
| 177.52.35.0/24 | Valid | Nonecovered by 177.52.32.0/22 | 168 25% |
| 177.52.164.0/24 | Valid | Nonecovered by 177.52.164.0/22 | 168 25% |
| 177.52.165.0/24 | Valid | Nonecovered by 177.52.164.0/22 | 168 25% |
| 177.52.166.0/24 | Valid | Nonecovered by 177.52.164.0/22 | 168 25% |
| 177.52.167.0/24 | Valid | Nonecovered by 177.52.164.0/22 | 168 25% |
| 177.52.32.0/23 | Valid | Nonecovered by 177.52.32.0/22 | 107 16% |
| 177.52.34.0/23 | Valid | Nonecovered by 177.52.32.0/22 | 107 16% |
| 177.52.164.0/23 | Valid | Nonecovered by 177.52.164.0/22 | 107 16% |
| 177.52.166.0/23 | Valid | Nonecovered by 177.52.164.0/22 | 107 16% |
| 177.52.32.0/22 | Valid | Other IRR onlyNTTCOM, RADB, TC | 672 100% |
| 177.52.164.0/22 | Valid | Other IRR onlyNTTCOM, RADB, TC | 672 100% |
AS-SET
AS262436'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 14 are in fix.csv.
- Route object: none12
- Route object: RIR2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 177.52.32.0/24 | No route object for it. A route object for 177.52.32.0/22 with origin AS262436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262436 in the RIR database for the space. |
| Route object: none | 177.52.33.0/24 | No route object for it. A route object for 177.52.32.0/22 with origin AS262436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262436 in the RIR database for the space. |
| Route object: none | 177.52.34.0/24 | No route object for it. A route object for 177.52.32.0/22 with origin AS262436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262436 in the RIR database for the space. |
| Route object: none | 177.52.35.0/24 | No route object for it. A route object for 177.52.32.0/22 with origin AS262436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262436 in the RIR database for the space. |
| Route object: none | 177.52.164.0/24 | No route object for it. A route object for 177.52.164.0/22 with origin AS262436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262436 in the RIR database for the space. |
| Route object: none | 177.52.165.0/24 | No route object for it. A route object for 177.52.164.0/22 with origin AS262436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262436 in the RIR database for the space. |
| Route object: none | 177.52.166.0/24 | No route object for it. A route object for 177.52.164.0/22 with origin AS262436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262436 in the RIR database for the space. |
| Route object: none | 177.52.167.0/24 | No route object for it. A route object for 177.52.164.0/22 with origin AS262436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262436 in the RIR database for the space. |
| Route object: none | 177.52.32.0/23 | No route object for it. A route object for 177.52.32.0/22 with origin AS262436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262436 in the RIR database for the space. |
| Route object: none | 177.52.34.0/23 | No route object for it. A route object for 177.52.32.0/22 with origin AS262436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262436 in the RIR database for the space. |
| Route object: none | 177.52.164.0/23 | No route object for it. A route object for 177.52.164.0/22 with origin AS262436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262436 in the RIR database for the space. |
| Route object: none | 177.52.166.0/23 | No route object for it. A route object for 177.52.164.0/22 with origin AS262436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262436 in the RIR database for the space. |
| Route object: RIR | 177.52.32.0/22 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.52.164.0/22 | Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS262436 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.