Network · data from 2026-11-12
AS271413 CASTRO TELECOM
Registry name: AS271413 - E O L CASTRO TELECOMUNICACOES EIRELI, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS271413, 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.4.124.0/24 | No ROA | Other origin onlycovered by 200.4.124.0/23 | 7 1%low visibility |
| 200.4.125.0/24 | No ROA | Nonecovered by 200.4.124.0/23 | 7 1%low visibility |
| 200.4.126.0/24 | No ROA | Other IRR onlyTC | 671 100% |
| 200.4.124.0/23 | No ROA | Other IRR onlyRADB | 667 99% |
| 2804:7b24::/32 | No ROA | Other IRR onlyRADB, TC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS271413: AS271413:AS-ANNOUNCEMENTS. 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 (AS271413 isn't in the set, or no route object for AS271413 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 | AS271413 in it | Not covered |
|---|---|---|---|---|---|
| AS271413:AS-ANNOUNCEMENTS | TC | 1 | 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 12 are in fix.csv.
- ROA: none5
- Route object: none2
- Route object: RIR3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 200.4.124.0/24 | No ROA covers it. Add a ROA for AS271413, maxLength 24. |
| Route object: none | 200.4.124.0/24 | Route objects for it name AS264014. A route object for 200.4.124.0/23 with origin AS271413 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271413 in the RIR database for the space. |
| ROA: none | 200.4.125.0/24 | No ROA covers it. Add a ROA for AS271413, maxLength 24. |
| Route object: none | 200.4.125.0/24 | No route object for it. A route object for 200.4.124.0/23 with origin AS271413 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271413 in the RIR database for the space. |
| ROA: none | 200.4.126.0/24 | No ROA covers it. Add a ROA for AS271413, maxLength 24. |
| Route object: RIR | 200.4.126.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 200.4.124.0/23 | No ROA covers it. Add a ROA for AS271413, maxLength 23. |
| Route object: RIR | 200.4.124.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:7b24::/32 | No ROA covers it. Add a ROA for AS271413, maxLength 32. |
| Route object: RIR | 2804:7b24::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS271413 whose prefix no peer sees AS271413 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.4.124.0/22 | RADB, TC | No ROA |
| 200.4.127.0/24 | 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.