bgpreport

Network · data from 2026-11-12

AS271204 STREET RECIFE SERVICO DE COMUNICACAO LTDA

Registry name: AS271204 - STREET RECIFE SERVICO DE COMUNICACAO LTDA, BR · PeeringDB

4IPv4 routes 100.0% RPKI valid · 75.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS271204, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS271204, 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:77dc::/34 No ROA Other IRR onlyRADB 633 100% 67
179.49.188.0/23 Valid Nonecovered by 179.49.188.0/22 671 100% 66
179.49.190.0/23 Valid Other IRR onlyRADB 672 100% 67
179.49.190.0/24 Valid Other IRR onlyALTDB, RADB 672 100% 67
179.49.191.0/24 Valid Other IRR onlyALTDB, RADB 672 100% 67

AS-SET

AS271204's PeeringDB record names no 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 13 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: RIR4
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none2804:77dc::/34No ROA covers it. Add a ROA for AS271204, maxLength 34.633 of 636
Route object: RIR2804:77dc::/34Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: none179.49.188.0/23No route object for it. A route object for 179.49.188.0/22 with origin AS271204 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271204 in the RIR database for the space.671 of 673
Route object: RIR179.49.190.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR179.49.190.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR179.49.191.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Route objects with origin AS271204 whose prefix no peer sees AS271204 announce. Many are kept on purpose (backup routes, space announced only in some places).

45.236.60.0/22RADBNo ROA
45.236.60.0/23RADBNo ROA
45.236.60.0/24RADBValid
45.236.62.0/23RADBNo ROA
45.236.63.0/24RADBNo ROA
179.49.188.0/22RADBNo ROA
2804:77dc::/32RADBNo 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.