Network · data from 2026-11-12
AS272626 N9 Telecom
Registry name: AS272626 - N9 TELECOM by Ligpronet, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS272626, 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:6e30:c000::/48 | Invalid: origin | None | 6 1%low visibility |
| 2804:862c:26ff::/48 | Invalid: maxLength | Nonecovered by 2804:862c::/32 | 73 11% |
| 216.28.130.0/24 | No ROA | None | 669 99% |
| 2804:862c::/33 | Valid | Nonecovered by 2804:862c::/32 | 358 56% |
| 2804:862c:8000::/33 | Valid | Nonecovered by 2804:862c::/32 | 358 56% |
| 2804:862c::/32 | Valid | Other IRR onlyTC | 631 99% |
AS-SET
PeeringDB's irr_as_set for AS272626: AS272626:AS-N9. 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 (AS272626 isn't in the set, or no route object for AS272626 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 | AS272626 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS272626:AS-N9 | 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 10 are in fix.csv.
- ROA: origin1
- ROA: maxLength1
- ROA: none1
- Route object: none5
- Route object: RIR1
- AS-SET: not found1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2804:6e30:c000::/48 | ROAs covering it name AS270581, not AS272626. If AS272626 should announce it, add a ROA for AS272626. |
| Route object: none | 2804:6e30:c000::/48 | No route object for it. Add a route object with origin AS272626 in the RIR database for the space. |
| ROA: maxLength | 2804:862c:26ff::/48 | ROA 2804:862c::/32 AS272626 has maxLength 32; ROA 2804:862c::/33 AS272626 has maxLength 33; the route is a /48. Raise the maxLength, or add a ROA for 2804:862c:26ff::/48. |
| Route object: none | 2804:862c:26ff::/48 | No route object for it. A route object for 2804:862c::/32 with origin AS272626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272626 in the RIR database for the space. |
| ROA: none | 216.28.130.0/24 | No ROA covers it. Add a ROA for AS272626, maxLength 24. |
| Route object: none | 216.28.130.0/24 | No route object for it. Add a route object with origin AS272626 in the RIR database for the space. |
| Route object: none | 2804:862c::/33 | No route object for it. A route object for 2804:862c::/32 with origin AS272626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272626 in the RIR database for the space. |
| Route object: none | 2804:862c:8000::/33 | No route object for it. A route object for 2804:862c::/32 with origin AS272626 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272626 in the RIR database for the space. |
| Route object: RIR | 2804:862c::/32 | Route object only in TC. Add it in the RIR database for the space. |
| AS-SET: not found | AS272626:AS-N9 | PeeringDB names AS272626:AS-N9; no IRR database read has it. |
Route objects not announced
Every route object with origin AS272626 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.