Network · data from 2026-11-12
AS263374 ROCHA, ANDRADE E DONEDA
Registry name: AS263374 - YZO TELECOM TECNOLOGIA EIRELI - ME, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263374, 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.38.85.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 177.38.87.0/24 | Valid | Other IRR onlyTC | 672 100% |
| 177.38.84.0/24 | Valid | Other IRR onlyTC | 671 100% |
| 191.37.224.0/21 | Valid | Other IRR onlyALTDB, RADB, TC | 669 99% |
| 191.37.224.0/22 | Valid | Other IRR onlyTC | 669 99% |
| 191.37.226.0/23 | Valid | Other IRR onlyTC | 669 99% |
| 191.37.224.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 191.37.228.0/22 | Valid | Other IRR onlyTC | 668 99% |
| 191.37.228.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 191.37.230.0/24 | Valid | Other IRR onlyTC | 666 99% |
| 177.38.84.0/22 | Valid | Other IRR onlyTC | 665 99% |
| 177.38.84.0/23 | Valid | Other IRR onlyTC | 665 99% |
| 177.38.86.0/23 | Valid | Other IRR onlyTC | 665 99% |
| 2804:1528::/32 | Valid | Other IRR onlyALTDB, RADB, TC | 352 55% |
| 2804:1528::/36 | Valid | Other IRR onlyTC | 349 55% |
| 2804:1528:f000::/36 | Valid | Other IRR onlyTC | 349 55% |
AS-SET
PeeringDB's irr_as_set for AS263374: AS263374:AS-ALL. 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 (AS263374 isn't in the set, or no route object for AS263374 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 | AS263374 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS263374:AS-ALL | In no IRR database read today. | |||||
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 28 are in fix.csv.
- Route object: RIR16
- AS-SET: not found1
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 177.38.85.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.87.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.84.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.37.224.0/21 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.37.224.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.37.226.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.37.224.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.37.228.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.37.228.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 191.37.230.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.84.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.84.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.38.86.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1528::/32 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1528::/36 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1528:f000::/36 | Route object only in TC. Add it in the RIR database for the space. |
| AS-SET: not found | AS263374:AS-ALL | PeeringDB names AS263374:AS-ALL; no IRR database read has it. |
Route objects not announced
Route objects with origin AS263374 whose prefix no peer sees AS263374 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.38.86.0/24 | TC | Valid |
| 191.37.224.0/24 | TC | Valid |
| 191.37.225.0/24 | TC | Valid |
| 191.37.226.0/24 | TC | Valid |
| 191.37.227.0/24 | RADB, TC | Valid |
| 191.37.228.0/24 | TC | Valid |
| 191.37.229.0/24 | TC | Valid |
| 191.37.230.0/23 | TC | Valid |
| 191.37.231.0/24 | TC | Valid |
| 2804:1528:500::/48 | TC | Valid |
| 2804:1528:2100::/48 | 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.