Network · data from 2026-11-12
AS271358 AP INTERNET
Registry name: AS271358 - AP INTERNET, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS271358, 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.
| 200.50.228.0/24 | No ROA | Other IRR onlyRADB, TC | 672 100% |
| 200.50.229.0/24 | No ROA | Other IRR onlyRADB, TC | 670 100% |
| 200.50.231.0/24 | No ROA | Other IRR onlyALTDB, RADB, TC | 670 100% |
| 200.50.230.0/24 | No ROA | Other IRR onlyRADB, TC | 666 99% |
| 2804:7a40::/34 | No ROA | Other IRR onlyTC | 635 100% |
| 2804:7a40:4000::/34 | No ROA | Other IRR onlyTC | 635 100% |
| 2804:7a40:c000::/34 | No ROA | Other IRR onlyALTDB, RADB, TC | 633 100% |
| 2804:7a40:8000::/34 | No ROA | Other IRR onlyTC | 631 99% |
AS-SET
PeeringDB's irr_as_set for AS271358: AS2271358:AS-SET. 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 (AS271358 isn't in the set, or no route object for AS271358 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 | AS271358 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS2271358:AS-SET | 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 21 are in fix.csv.
- ROA: none8
- Route object: RIR8
- AS-SET: not found1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 200.50.228.0/24 | No ROA covers it. Add a ROA for AS271358, maxLength 24. |
| Route object: RIR | 200.50.228.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 200.50.229.0/24 | No ROA covers it. Add a ROA for AS271358, maxLength 24. |
| Route object: RIR | 200.50.229.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 200.50.231.0/24 | No ROA covers it. Add a ROA for AS271358, maxLength 24. |
| Route object: RIR | 200.50.231.0/24 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 200.50.230.0/24 | No ROA covers it. Add a ROA for AS271358, maxLength 24. |
| Route object: RIR | 200.50.230.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:7a40::/34 | No ROA covers it. Add a ROA for AS271358, maxLength 34. |
| Route object: RIR | 2804:7a40::/34 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 2804:7a40:4000::/34 | No ROA covers it. Add a ROA for AS271358, maxLength 34. |
| Route object: RIR | 2804:7a40:4000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 2804:7a40:c000::/34 | No ROA covers it. Add a ROA for AS271358, maxLength 34. |
| Route object: RIR | 2804:7a40:c000::/34 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:7a40:8000::/34 | No ROA covers it. Add a ROA for AS271358, maxLength 34. |
| Route object: RIR | 2804:7a40:8000::/34 | Route object only in TC. Add it in the RIR database for the space. |
| AS-SET: not found | AS2271358:AS-SET | PeeringDB names AS2271358:AS-SET; no IRR database read has it. |
Route objects not announced
Route objects with origin AS271358 whose prefix no peer sees AS271358 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.50.228.0/22 | RADB, TC | No ROA |
| 200.50.228.0/23 | RADB, TC | No ROA |
| 200.50.230.0/23 | RADB, TC | No ROA |
| 2804:7a40::/32 | RADB, 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.