bgpreport

Network · data from 2026-11-12

AS270855 AS270855 - J.Z COSTA SILVA ME

Registry name: AS270855 - J.Z COSTA SILVA ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270855, 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.
179.43.59.0/24 No ROA Nonecovered by 179.43.56.0/22 670 100% 67
179.43.58.0/24 No ROA Nonecovered by 179.43.56.0/22 669 99% 67
179.43.56.0/24 No ROA Nonecovered by 179.43.56.0/23 2 0%low visibility 2
179.43.57.0/24 No ROA Nonecovered by 179.43.56.0/23 2 0%low visibility 2

AS-SET

AS270855 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 12 are in fix.csv.

  • ROA: none4
  • Route object: none4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none179.43.59.0/24No ROA covers it. Add a ROA for AS270855, maxLength 24.670 of 673
Route object: none179.43.59.0/24No route object for it. A route object for 179.43.56.0/22 with origin AS270855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270855 in the RIR database for the space.670 of 673
ROA: none179.43.58.0/24No ROA covers it. Add a ROA for AS270855, maxLength 24.669 of 673
Route object: none179.43.58.0/24No route object for it. A route object for 179.43.56.0/22 with origin AS270855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270855 in the RIR database for the space.669 of 673
ROA: none179.43.56.0/24No ROA covers it. Add a ROA for AS270855, maxLength 24.2 of 673
Route object: none179.43.56.0/24No route object for it. A route object for 179.43.56.0/23 with origin AS270855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270855 in the RIR database for the space.2 of 673
ROA: none179.43.57.0/24No ROA covers it. Add a ROA for AS270855, maxLength 24.2 of 673
Route object: none179.43.57.0/24No route object for it. A route object for 179.43.56.0/23 with origin AS270855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270855 in the RIR database for the space.2 of 673

Route objects not announced

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

179.43.56.0/22RADBNo ROA
179.43.56.0/23RADBNo ROA
2804:727c::/32RADBNo ROA
2804:727c::/33RADBNo 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.