bgpreport

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

5IPv4 routes 40.0% RPKI valid · 80.0% with a route object
4IPv6 routes 50.0% RPKI valid · 25.0% with a route object
2RPKI invalid 0 origin · 2 maxLength
3No ROA 4 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS270524, seen from no peer

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% 42
2804:6d50:4000::/34 Invalid: maxLength Nonecovered by 2804:6d50::/33 82 13% 42
187.103.200.0/23 No ROA Other IRR onlyRADB 670 100% 66
187.103.201.0/24 No ROA Other IRR onlyRADB 670 100% 66
187.103.200.0/24 No ROA Other IRR onlyRADB 560 83% 65
187.103.202.0/24 Valid Nonecovered by 187.103.202.0/23 671 100% 66
2804:6d50:c000::/34 Valid Nonecovered by 2804:6d50::/32 636 100% 67
187.103.203.0/24 Valid Other IRR onlyRADB 672 100% 66
2804:6d50::/33 Valid Other IRR onlyRADB 635 100% 67

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
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:6d50::/34ROA 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.82 of 636
Route object: none2804:6d50::/34No 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.82 of 636
ROA: maxLength2804:6d50:4000::/34ROA 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.82 of 636
Route object: none2804:6d50:4000::/34No 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.82 of 636
ROA: none187.103.200.0/23No ROA covers it. Add a ROA for AS270524, maxLength 23.670 of 673
Route object: RIR187.103.200.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none187.103.201.0/24No ROA covers it. Add a ROA for AS270524, maxLength 24.670 of 673
Route object: RIR187.103.201.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none187.103.200.0/24No ROA covers it. Add a ROA for AS270524, maxLength 24.560 of 673
Route object: RIR187.103.200.0/24Route object only in RADB. Add it in the RIR database for the space.560 of 673
Route object: none187.103.202.0/24No 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.671 of 673
Route object: none2804:6d50:c000::/34No 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.636 of 636
Route object: RIR187.103.203.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:6d50::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636

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/22RADB, TCNo ROA
187.103.202.0/23RADBNo ROA
2804:6d50::/32RADB, TCValid

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.