Network · data from 2026-11-12
AS273481 NC SERVICOS E TELECOMUNICACOES LTDA
Registry name: AS273481 - NC SERVICOS E TELECOMUNICACOES LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS273481, 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:8f48:a000::/40 | No ROA | Nonecovered by 2804:8f48:8000::/34 | 631 99% |
| 186.227.186.0/23 | No ROA | Other IRR onlyTC | 671 100% |
| 186.227.186.0/24 | No ROA | Other IRR onlyRADB, TC | 667 99% |
| 186.227.187.0/24 | No ROA | Other IRR onlyRADB, TC | 667 99% |
| 2804:8f48::/32 | No ROA | Other IRR onlyRADB, TC | 630 99% |
AS-SET
PeeringDB's irr_as_set for AS273481: AS273481:AS-GLOBAL. 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 (AS273481 isn't in the set, or no route object for AS273481 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 | AS273481 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS273481:AS-GLOBAL | 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 17 are in fix.csv.
- ROA: none5
- Route object: none1
- Route object: RIR4
- AS-SET: not found1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:8f48:a000::/40 | No ROA covers it. Add a ROA for AS273481, maxLength 40. |
| Route object: none | 2804:8f48:a000::/40 | No route object for it. A route object for 2804:8f48:8000::/34 with origin AS273481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273481 in the RIR database for the space. |
| ROA: none | 186.227.186.0/23 | No ROA covers it. Add a ROA for AS273481, maxLength 23. |
| Route object: RIR | 186.227.186.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 186.227.186.0/24 | No ROA covers it. Add a ROA for AS273481, maxLength 24. |
| Route object: RIR | 186.227.186.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 186.227.187.0/24 | No ROA covers it. Add a ROA for AS273481, maxLength 24. |
| Route object: RIR | 186.227.187.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:8f48::/32 | No ROA covers it. Add a ROA for AS273481, maxLength 32. |
| Route object: RIR | 2804:8f48::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| AS-SET: not found | AS273481:AS-GLOBAL | PeeringDB names AS273481:AS-GLOBAL; no IRR database read has it. |
Route objects not announced
Route objects with origin AS273481 whose prefix no peer sees AS273481 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:8f48::/33 | TC | No ROA |
| 2804:8f48::/34 | TC | No ROA |
| 2804:8f48:4000::/34 | TC | No ROA |
| 2804:8f48:8000::/33 | TC | No ROA |
| 2804:8f48:8000::/34 | TC | No ROA |
| 2804:8f48:c000::/34 | TC | No ROA |
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.