Network · data from 2026-11-12
AS264010 Polli Telecom
Registry name: AS264010 - Polli Telecom, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264010, 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.54.80.0/20 | No ROA | Other IRR onlyRADB | 672 100% |
| 2804:2958:3f00::/40 | Valid | Nonecovered by 2804:2958::/32 | 631 99% |
| 143.0.198.0/23 | Valid | Nonecovered by 143.0.196.0/22 | 119 18% |
| 143.0.196.0/23 | Valid | Nonecovered by 143.0.196.0/22 | 118 18% |
| 143.0.196.0/22 | Valid | Other IRR onlyALTDB, RADB, TC | 672 100% |
| 177.54.84.0/22 | Valid | Other IRR onlyRADB | 671 100% |
| 177.54.92.0/22 | Valid | Other IRR onlyRADB | 671 100% |
| 177.54.80.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 177.54.89.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 177.54.92.0/23 | Valid | Other IRR onlyRADB | 668 99% |
| 177.54.85.0/24 | Valid | Other IRR onlyRADB | 666 99% |
| 2804:2958::/32 | Valid | Other IRR onlyALTDB, RADB, TC | 636 100% |
| 177.54.86.0/23 | Valid | Other IRR onlyRADB | 118 18% |
| 177.54.84.0/23 | Valid | Other IRR onlyRADB | 117 17% |
| 177.54.94.0/23 | Valid | Other IRR onlyRADB | 117 17% |
| 177.54.90.0/23 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 177.54.91.0/24 | Valid | Other IRR onlyRADB | 2 0%low visibility |
| 177.54.90.0/24 | Valid | Other IRR onlyRADB | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS264010: AS-264010. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS264010 isn't in the set, or no route object for AS264010 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS264010 in it | Not covered |
|---|---|---|---|---|---|
| AS-264010 | ALTDB | 8 | 2 | Yes | 0 |
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 38 are in fix.csv.
- ROA: none1
- Route object: none3
- Route object: RIR15
- Route object: not announced19
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 177.54.80.0/20 | No ROA covers it. Add a ROA for AS264010, maxLength 20. |
| Route object: RIR | 177.54.80.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 2804:2958:3f00::/40 | No route object for it. A route object for 2804:2958::/32 with origin AS264010 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264010 in the RIR database for the space. |
| Route object: none | 143.0.198.0/23 | No route object for it. A route object for 143.0.196.0/22 with origin AS264010 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264010 in the RIR database for the space. |
| Route object: none | 143.0.196.0/23 | No route object for it. A route object for 143.0.196.0/22 with origin AS264010 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264010 in the RIR database for the space. |
| Route object: RIR | 143.0.196.0/22 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.54.84.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.54.92.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.54.80.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.54.89.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.54.92.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.54.85.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2958::/32 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.54.86.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.54.84.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.54.94.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.54.90.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.54.91.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.54.90.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS264010 whose prefix no peer sees AS264010 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 143.0.196.0/24 | ALTDB | Valid |
| 143.0.197.0/24 | ALTDB | Valid |
| 177.54.80.0/21 | RADB | No ROA |
| 177.54.80.0/22 | RADB | No ROA |
| 177.54.80.0/23 | RADB | No ROA |
| 177.54.81.0/24 | RADB | No ROA |
| 177.54.82.0/23 | RADB | No ROA |
| 177.54.82.0/24 | RADB | No ROA |
| 177.54.83.0/24 | RADB | No ROA |
| 177.54.84.0/24 | RADB | Valid |
| 177.54.86.0/24 | RADB | Valid |
| 177.54.87.0/24 | RADB | Valid |
| 177.54.88.0/21 | RADB | No ROA |
| 177.54.88.0/22 | RADB | No ROA |
| 177.54.88.0/23 | RADB | No ROA |
| 177.54.92.0/24 | RADB | Valid |
| 177.54.93.0/24 | RADB | Valid |
| 177.54.94.0/24 | RADB | Valid |
| 177.54.95.0/24 | RADB | 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.