Planned maintenance: Infrastructure upgrade (May 9–10, 2026)

Modified on Wed, Apr 29 at 9:24 AM

Ottimate will perform a scheduled infrastructure upgrade over the weekend of May 9–10, 2026.
This article outlines what to expect, when services may be affected, and answers common questions.

Maintenance schedule (all times Eastern)

Saturday, May 9 — 3:30 AM ET · Report data pauses

  • Reports at reports.plateiq.com will temporarily stop receiving new data. The platform remains accessible, but reports will not reflect new activity until the upgrade is complete.

Sunday, May 10 — 1:30 AM ET · Final switchover begins 

  • The primary maintenance window opens (~3 hours). You may experience slowness or brief interruptions. We recommend avoiding time-sensitive tasks (invoice submissions, payment processing) during this window.

Sunday, May 10 — 4:30 AM ET · Maintenance complete

  • The upgrade is expected to be complete. Full platform functionality is restored.

Sunday, May 10 — by 8:30 AM ET · Reports fully up to date

  •  Reports will resume receiving data and will be fully caught up.

What is affected

Reports 

  • Data stops refreshing starting May 9 at 3:30 AM ET

  • Historical data remains visible

  • New data appears after the upgrade completes and backfills automatically

Platform 

  • Fully accessible before the maintenance window

  • During May 10, 1:30 AM – 4:30 AM ET, you may experience slowness or brief interruptions

  • Avoid critical workflows during this time if possible

Your data

  • No data will be lost

  • All invoices, payments, and vendor data remain fully protected

  • Activity during the window will be reflected once reports catch up

Why is this happening

We’re upgrading a core database component to improve performance, reliability, and long-term security. This ensures a faster, more stable experience across the platform.

How to monitor status

You can track real-time updates here:  https://status.ottimate.com/

Frequently asked questions

Will I lose any data? No. Your data is fully protected throughout this process. No invoices, payment records, or vendor information will be affected.

Will I be completely locked out of Ottimate? Not necessarily. You may experience slowness or brief interruptions, but we are working to keep any disruption to a minimum. We recommend avoiding critical workflows during this window as a precaution.

Why are my reports showing older data starting May 9? As part of our upgrade preparation, we temporarily pause the data pipeline that feeds your reports. This is a necessary step in the process and ensures a safe, accurate upgrade. All data from this period will be reflected correctly in your reports once the upgrade is complete.

Why is this happening? We are upgrading a core part of our infrastructure to a newer, more powerful version. This upgrade improves system stability, performance, and long-term security — all of which benefit you directly.

How long will the data gap in the report last? Reports will stop refreshing starting May 9 at 3:30 AM EDT. Once the upgrade is complete, the reports platform will start receiving data again and will be fully caught up by May 10 8:30 AM EDT.

How long will this take? 3 hours. The final switchover starts Sunday, May 10, at 1:30 AM EDT and ends at 4:30 AM EDT. During that time, avoid using the dashboard.

What if I need to process something urgently during this time? We recommend completing any urgent tasks before Saturday, May 9th. If you have a critical need during the window, contact your Customer Success Manager directly.

Where can I check the current status of Ottimate? You can monitor the platform's live status at https://status.ottimate.com/. We will update that page when maintenance begins and again when it is complete.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article