bgpreport

Network · data from 2026-11-12

AS60014 ABRAMAD Abramad Technological Infrastructures Development Company PJS

Registry name: ABRAMAD Abramad Technological Infrastructures Development Company PJS, IR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS60014, 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.
193.106.190.0/24 Invalid: origin Other origin only 1 0%low visibility 1
78.31.232.0/23 Valid RIR databaseRIPE 671 100% 67
78.31.234.0/23 Valid RIR databaseRIPE 671 100% 67
185.119.240.0/24 Valid RIR databaseRIPE 671 100% 67
185.119.241.0/24 Valid RIR databaseRIPE 671 100% 67
185.187.85.0/24 Valid RIR databaseRIPE 671 100% 67
185.119.242.0/23 Valid RIR databaseRIPE 670 100% 66

AS-SET

AS60014 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 4 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin193.106.190.0/24ROAs covering it name AS211325, not AS60014. If AS60014 should announce it, add a ROA for AS60014.1 of 673
Route object: none193.106.190.0/24Route objects for it name AS211325. Add a route object with origin AS60014 in the RIR database for the space.1 of 673

Route objects not announced

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

78.31.232.0/22RIPEValid
185.119.240.0/22RIPEValid

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.