Network · data from 2026-11-12
AS61580 NIC.br - OpenCDN
Registry name: AS61580 - Nucleo de Inf. e Coord. do Ponto BR - NIC.BR, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61580, 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.
| 168.181.20.0/24 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 168.181.20.0/22 | Valid | Other IRR onlyRADB, TC | 664 99% |
| 200.192.104.0/24 | Valid | Other IRR onlyTC | 664 99% |
| 2801:80:1700::/40 | Valid | Other IRR onlyRADB, TC | 635 100% |
| 2801:80:17a0::/48 | Valid | Other IRR onlyRADB, TC | 635 100% |
| 168.181.21.0/24 | Valid | Other IRR onlyTC | 17 3%low visibility |
| 2801:80:17b2::/48 | Valid | Other IRR onlyTC | 5 1%low visibility |
| 2801:80:17b0::/48 | Valid | Other IRR onlyTC | 3 0%low visibility |
| 2801:80:17df::/48 | Valid | Other IRR onlyTC | 3 0%low visibility |
| 2801:80:179e::/48 | Valid | Other IRR onlyTC | 2 0%low visibility |
| 168.181.22.0/24 | Valid | Other IRR onlyTC | 1 0%low visibility |
| 2.21.67.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 2.22.51.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 2600:1419:8::/48 | Valid | RIR databaseARIN | 635 100% |
| 2600:1419:7200::/48 | Valid | RIR databaseARIN | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS61580: AS61580: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 (AS61580 isn't in the set, or no route object for AS61580 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 | AS61580 in it | Not covered |
|---|---|---|---|---|---|
| AS61580:AS-ALL | TC | 3 | 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 14 are in fix.csv.
- Route object: RIR11
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 168.181.20.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.181.20.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 200.192.104.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2801:80:1700::/40 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2801:80:17a0::/48 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.181.21.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2801:80:17b2::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2801:80:17b0::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2801:80:17df::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2801:80:179e::/48 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 168.181.22.0/24 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61580 whose prefix no peer sees AS61580 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 168.181.23.0/24 | RADB, TC | Valid |
| 2600:1419:e800::/48 | ARIN | Valid |
| 2801:80:17be::/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.