Earthdata Forum

This morning, when I ran INSAR_GAMMA SLC on HyP3, it failed. I also tried changing the looks from 10×2 to 20×4, but it still resulted in an error. Is there possibly an issue occurring on HyP3?

**Additional information**

This pair worked successfully:

* Reference Granule: S1C_IW_SLC__1SDV_20260404T082550_20260404T082617_007064_00E4D3_7FDB
* Secondary Granule: S1C_IW_SLC__1SDV_20260416T082551_20260416T082618_007239_00EAB9_8F47

However, when I used the secondary from the above pair as the reference, and set the latest acquisition as the secondary, it resulted in an error:

* Secondary (latest acquisition): S1C_IW_SLC__1SDV_20260428T082552_20260428T082619_007414_00F0A7_D6DD

Is there any known issue that could be causing this?

When I attempted to generate pairs in SBAS processing, I encountered an error message as shown in the attached screenshot( 2026/04/28 data error happen)

For reference, in the previous scene of the same dataset(2026/04/16 data), pair generation succeeds, but the baseline is shown as 0 m.

It seems that the baseline may not be calculated correctly.

Thanks for reporting this issue!

There are currently no Precise Orbit Determination (POD) products available for S1C from Apr 28 08:15:17 - 13:11:30 UTC time.

SBAS computations and InSAR processing using HyP3 require at least an AUX_RESORB POD product be available. Your granule falls in this window (Apr 28 08:25:52) which is causing your requests to fail.

This may be related to the loss of S1C data on Apr 28 described at https://dataspace.copernicus.eu/news/2026-4-29-copernicus-sentinel-1c-data-unavailability-28-april-2026. Your requests should start working if/when Copernicus publishes POD data for the missing time window. The typical schedule would have an AUX_POEORB product covering all of Apr 28 published on/around May 16.

Thank you for the information.
For now, I tried a different scene, and the one observed yesterday was processed successfully without any issues.