bgpreport

Network · data from 2026-11-12

AS27870 AS27870 - FABRONI CLAUDIO ANTONIO

Registry name: AS27870 - FABRONI CLAUDIO ANTONIO, AR · not in PeeringDB

9IPv4 routes 88.9% RPKI valid · 44.4% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
0No ROA 5 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS27870, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS27870, 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.60.223.0/24 Invalid: origin None 1 0%low visibility 1
200.110.210.0/24 Valid None 668 99% 67
200.110.211.0/24 Valid None 668 99% 67
200.110.208.0/24 Valid None 667 99% 67
200.110.209.0/24 Valid None 667 99% 67
200.110.212.0/24 Valid Other IRR onlyRADB 671 100% 67
200.110.213.0/24 Valid Other IRR onlyRADB 671 100% 67
200.110.214.0/24 Valid Other IRR onlyRADB 671 100% 67
200.110.215.0/24 Valid Other IRR onlyRADB 671 100% 67

AS-SET

AS27870 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 11 are in fix.csv.

  • ROA: origin1
  • Route object: none5
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin179.60.223.0/24ROAs covering it name AS269795, not AS27870. If AS27870 should announce it, add a ROA for AS27870.1 of 673
Route object: none179.60.223.0/24No route object for it. Add a route object with origin AS27870 in the RIR database for the space.1 of 673
Route object: none200.110.210.0/24No route object for it. Add a route object with origin AS27870 in the RIR database for the space.668 of 673
Route object: none200.110.211.0/24No route object for it. Add a route object with origin AS27870 in the RIR database for the space.668 of 673
Route object: none200.110.208.0/24No route object for it. Add a route object with origin AS27870 in the RIR database for the space.667 of 673
Route object: none200.110.209.0/24No route object for it. Add a route object with origin AS27870 in the RIR database for the space.667 of 673
Route object: RIR200.110.212.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.110.213.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.110.214.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.110.215.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

2803:a880::/32RADBValid

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.