Network · data from 2026-11-12
AS270524 AS270524 - R J C DA SILVA SERVICOS
Registry name: AS270524 - R J C DA SILVA SERVICOS, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270524, 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:6d50::/34 | Invalid: maxLength | Nonecovered by 2804:6d50::/33 | 82 13% |
| 2804:6d50:4000::/34 | Invalid: maxLength | Nonecovered by 2804:6d50::/33 | 82 13% |
| 187.103.200.0/23 | No ROA | Other IRR onlyRADB | 670 100% |
| 187.103.201.0/24 | No ROA | Other IRR onlyRADB | 670 100% |
| 187.103.200.0/24 | No ROA | Other IRR onlyRADB | 560 83% |
| 187.103.202.0/24 | Valid | Nonecovered by 187.103.202.0/23 | 671 100% |
| 2804:6d50:c000::/34 | Valid | Nonecovered by 2804:6d50::/32 | 636 100% |
| 187.103.203.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 2804:6d50::/33 | Valid | Other IRR onlyRADB | 635 100% |
AS-SET
AS270524 isn't in PeeringDB, where networks name their AS-SET.
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: maxLength2
- ROA: none3
- Route object: none4
- Route object: RIR5
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 2804:6d50::/34 | ROA 2804:6d50::/32 AS270524 has maxLength 32; ROA 2804:6d50::/33 AS270524 has maxLength 33; the route is a /34. Raise the maxLength, or add a ROA for 2804:6d50::/34. |
| Route object: none | 2804:6d50::/34 | No route object for it. A route object for 2804:6d50::/33 with origin AS270524 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270524 in the RIR database for the space. |
| ROA: maxLength | 2804:6d50:4000::/34 | ROA 2804:6d50::/32 AS270524 has maxLength 32; ROA 2804:6d50::/33 AS270524 has maxLength 33; the route is a /34. Raise the maxLength, or add a ROA for 2804:6d50:4000::/34. |
| Route object: none | 2804:6d50:4000::/34 | No route object for it. A route object for 2804:6d50::/33 with origin AS270524 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270524 in the RIR database for the space. |
| ROA: none | 187.103.200.0/23 | No ROA covers it. Add a ROA for AS270524, maxLength 23. |
| Route object: RIR | 187.103.200.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 187.103.201.0/24 | No ROA covers it. Add a ROA for AS270524, maxLength 24. |
| Route object: RIR | 187.103.201.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 187.103.200.0/24 | No ROA covers it. Add a ROA for AS270524, maxLength 24. |
| Route object: RIR | 187.103.200.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 187.103.202.0/24 | No route object for it. A route object for 187.103.202.0/23 with origin AS270524 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270524 in the RIR database for the space. |
| Route object: none | 2804:6d50:c000::/34 | No route object for it. A route object for 2804:6d50::/32 with origin AS270524 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270524 in the RIR database for the space. |
| Route object: RIR | 187.103.203.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6d50::/33 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS270524 whose prefix no peer sees AS270524 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 187.103.200.0/22 | RADB, TC | No ROA |
| 187.103.202.0/23 | RADB | No ROA |
| 2804:6d50::/32 | RADB, 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.