bgpreport

Network · data from 2026-11-12

AS37026 Salt Essential Information Technology - Salt Essential Information Technology

Registry name: Salt Essential Information Technology - Salt Essential Information Technology, NA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS37026, 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.
41.190.86.0/23 No ROA Nonecovered by 41.190.84.0/22 669 99% 67
41.190.84.0/22 No ROA Other IRR onlyRIPE-NONAUTH 672 100% 67
41.190.84.0/23 No ROA Other IRR onlyRIPE-NONAUTH 669 99% 67

AS-SET

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

  • ROA: none3
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none41.190.86.0/23No ROA covers it. Add a ROA for AS37026, maxLength 23.669 of 673
Route object: none41.190.86.0/23No route object for it. A route object for 41.190.84.0/22 with origin AS37026 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37026 in the RIR database for the space.669 of 673
ROA: none41.190.84.0/22No ROA covers it. Add a ROA for AS37026, maxLength 22.672 of 673
Route object: RIR41.190.84.0/22Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.672 of 673
ROA: none41.190.84.0/23No ROA covers it. Add a ROA for AS37026, maxLength 23.669 of 673
Route object: RIR41.190.84.0/23Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

41.190.84.0/24RIPE-NONAUTHNo 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.