US & EU: Intermittent Microsoft Graph Errors Creating Calendars & Events
Update - The issue remains ongoing, with no change in behavior observed. We have submitted a Severity A support ticket with Microsoft and are currently awaiting their response regarding the Graph API errors impacting a subset of calendar and event creation requests.

Our engineering team continues to monitor closely and will provide updates as soon as new information becomes available.
Jun 23, 2025 - 14:03 PDT
Identified - We are seeing `ErrorInternalServerError` API errors from a small number of Microsoft grants when attempting to create new events or new calendars in the Nylas API.

We have confirmed that these errors are coming from Microsoft Graph API email servers and have reached out to Microsoft to address this issue.

Additionally, if you retry a failed API call to create a new calendar, a different error 409 `ErrorFolderExists` may be returned. This error is also from Microsoft Graph API.

This does not appear to be affecting any on-premise Exchange (EWS) grants or other email providers.
Jun 23, 2025 - 10:55 PDT
Temporary workaround in place for Microsoft Graph API issue
Update - We’ve received confirmation from Microsoft that their backend team has made partial progress toward resolving the upstream Graph Calendar API issue. Specifically, they’ve reported that the API fix is approximately halfway saturated through their infrastructure.

Microsoft has extended the tentative ETA for full production rollout to June 30, 2025.

In the meantime, our existing workaround remains in place, and core functionality continues to operate with minimal disruption. We will continue to monitor for any changes and provide updates as we receive them from Microsoft.

Thanks for your continued patience
Jun 17, 2025 - 18:29 PDT
Update - We’re still monitoring the issue impacting Microsoft’s Graph Calendar API, which affects access to some calendar data.

Microsoft has completed internal testing and is now working on finalizing a fix. Although this issue lies outside of our product, we remain in close communication with their support team and are pushing for timely updates.

We’ll continue to share more information as it becomes available. Thanks for your patience.
Jun 06, 2025 - 10:07 PDT
Update - We’ve been in contact with Microsoft support regarding the ongoing issue with their Graph Calendar API. Microsoft has acknowledged the problem and confirmed that their engineering team is actively working on a resolution.

We’ll continue to monitor the situation and provide updates as new information becomes available. Thank you for your patience.
Jun 04, 2025 - 10:21 PDT
Monitoring - We’ve implemented a workaround to mitigate the impact caused by an issue with Microsoft Graph API. As a result, the affected functionality has been restored, and users should no longer experience errors when accessing related features.

Please note that this is a temporary mitigation, and the root cause remains unresolved on Microsoft’s side. We are actively monitoring for updates and will revert our changes once Microsoft provides a permanent fix.

We appreciate your patience and will continue to keep you informed.
Jun 03, 2025 - 10:04 PDT
Update - We are still observing the ongoing issue with the Microsoft Graph API, which continues to affect some Microsoft grants. Impacted users may experience 500 and 504 errors on calendar-related endpoints, including delays or failures in webhook delivery.

As of now, there has been no resolution or update from Microsoft. Our team will continue monitoring and will provide further updates as soon as we detect meaningful changes.

This will be our final status page update for today unless there is a significant development. Thank you for your patience.
Jun 02, 2025 - 17:30 PDT
Update - We are continuing to monitor the ongoing issue with the Microsoft Graph API, which is impacting some Microsoft grants. The issue is still causing 500 and 504 errors on calendar-related endpoints, and delays or failures in webhook delivery for affected users.

There has been no meaningful change since our last update. Our team remains in contact with Microsoft and is actively monitoring for improvements. We will provide further updates as soon as we see progress or receive new information.
Jun 02, 2025 - 16:13 PDT
Identified - We are currently experiencing service degradation caused by an issue with the Microsoft Graph API. As a result, some Microsoft graph grants are experiencing 500 and 504 errors. For affected users, this may impact webhooks and the following API calls:

calendars
event
scheduler

Our team is actively monitoring the situation and has reported the issue to Microsoft. We will continue to provide updates as more information becomes available
Jun 02, 2025 - 12:00 PDT

About This Site

Seeing issues that aren't reflected on this page? Contact us at support@nylas.com

Nylas Application Services Operational
API v3 ? Operational
Webhooks v3 ? Operational
Authentication v3 ? Operational
Notetaker ? Operational
Scheduler v3 ? Operational
Dashboard v3 ? Operational
IMAP v3 ? Operational
Data Connectors v3 Operational
3rd Party Providers Degraded Performance
Microsoft 365 ? Degraded Performance
Outlook.com ? Degraded Performance
Google ? Operational
Yahoo! ? Operational
iCloud ? Operational
Other Email Server Hosting Providers ? Operational
Mailgun ? Operational
Oxylabs ? Operational
Cloudflare ? Operational
Subprocessors Operational
* Subprocessor Change Notification ? Operational
AWS ? Operational
GCP ? Operational
AssemblyAI ? Operational
Atlassian Pty Ltd ? Operational
Apollo ? Operational
CloudFlare ? Operational
Coralogix ? Operational
DataGroomr ? Operational
Datasiv ? Operational
Discourse ? Operational
Fastly ? Operational
FiveTran ? Operational
Gong.io ? Operational
Google ? Operational
Google ? Operational
Gravitational (Teleport) ? Operational
Honeycomb.io ? Operational
Hubspot ? Operational
Inflection.io ? Operational
Ketch ? Operational
Looker ? Operational
Madkudu ? Operational
Mailgun ? Operational
Microsoft ? Operational
New Relic ? Operational
PandaDoc ? Operational
PartnerPortal ? Operational
PlayerZero ? Operational
RB2B ? Operational
Recurly Inc. ? Operational
Rootly, Inc. ? Operational
Salesforce ? Operational
Salesloft ? Operational
Slack ? Operational
Strac ? Operational
Stripe ? Operational
Tropic ? Operational
Twilio Segment ? Operational
Vercel ? Operational
Vitally ? Operational
Whistic ? Operational
Woopra ? Operational
Zendesk ? Operational
Zoom ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Jun 24, 2025

No incidents reported today.

Jun 23, 2025

Unresolved incident: US & EU: Intermittent Microsoft Graph Errors Creating Calendars & Events.

Jun 22, 2025

No incidents reported.

Jun 21, 2025

No incidents reported.

Jun 20, 2025

No incidents reported.

Jun 19, 2025

No incidents reported.

Jun 18, 2025
[Scheduled Maintenance] US - API v3 - Service Optimization
Completed - The scheduled maintenance has been completed.
Jun 18, 19:00 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 18, 17:00 PDT
Scheduled - We are performing a system update to enhance the reliability and efficiency of our services. While we do not anticipate downtime during the maintenance window, there is a chance for elevated errors over normal levels. We appreciate your understanding as we continue to optimize our infrastructure.

If you have any questions or concerns, please contact our support team (support@nylas.com).
Jun 11, 10:45 PDT
Jun 17, 2025

Unresolved incident: Temporary workaround in place for Microsoft Graph API issue.

Jun 16, 2025

No incidents reported.

Jun 15, 2025

No incidents reported.

Jun 14, 2025

No incidents reported.

Jun 13, 2025

No incidents reported.

Jun 12, 2025
US & EU: Service Degradation – Elevated Latencies and Errors Affecting Primarily Google & Microsoft Accounts
Resolved - Google has confirmed that the remaining residual impact is limited to services that should not affect Nylas operations, including Dataflow in us-central1, Vertex AI Online Prediction, and Personalized Service Health.


Nylas services have remained stable, and all components are fully operational.

We are marking this incident as Resolved, but our team will continue to monitor closely in coordination with Google’s ongoing updates (https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW).

Thank you for your patience throughout this incident.
Jun 12, 17:38 PDT
Update - As of 1:45 PM PDT, Google has confirmed that most Google Cloud products are fully recovered. Some residual impact remains for a few services still marked as affected on their status dashboard (https://www.google.com/appsstatus/dashboard/), and Google is continuing to monitor those individually.

Their next update is expected by 4:00 PM PDT.

Nylas services remain stable, and we continue to monitor closely. We’ll provide a final update once full recovery is confirmed across all systems.
Jun 12, 15:34 PDT
Update - Google has confirmed that most Google Cloud products have fully recovered. A few services are still experiencing minor residual impact, and the respective engineering teams are actively working toward full restoration.

Google expects recovery to complete within the next hour and will post their next update by 3:00 PM PDT.

We continue to see stable performance across Nylas services and will share a final update once full recovery is confirmed.
Jun 12, 14:23 PDT
Update - Google has implemented mitigation measures for the issues in us-central1 and multi-region/us and is now seeing signs of recovery. Internal monitoring and customer reports confirm improvements across multiple regions, including early signs of recovery in the remaining impacted areas.

Google currently expects recovery to complete within the next hour and will provide their next update by 2:30 PM PDT.

We are seeing an almost full recovery as well, and will continue to monitor the situation closely and will provide a final update once full stability is confirmed.
Jun 12, 14:05 PDT
Update - All Nylas components are now operational, and performance levels are returning to normal. While recovery appears stable, we are continuing to monitor closely before marking the incident as fully resolved.

We are also working through a backlog of email webhooks for Microsoft and IMAP accounts caused by Google Pub/Sub outages during the incident.

We’ll provide a final update once sustained stability is confirmed.
Jun 12, 13:49 PDT
Update - We are now seeing signs of recovery in the us-central1 region as well. Error rates and latency continue to improve across affected Google Workspace services.

We’ll continue to monitor closely and provide another update after Google’s next scheduled post at 2:00 PM PDT, or sooner if full recovery is confirmed.
Jun 12, 13:29 PDT
Update - Google has confirmed that their infrastructure has recovered in all regions except us-central1. Cloud products dependent on the affected infrastructure are recovering in multiple locations.

“Our engineers have identified the root cause and applied appropriate mitigations. Our infrastructure has recovered in all regions except us-central1. Google Cloud products that rely on the affected infrastructure are seeing recovery in multiple locations. Our engineers are aware of the customers still experiencing issues on us-central1 and multi-region/us and are actively working on full recovery. We do not have an ETA for full recovery.”

You can follow Google’s live updates at: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW

We’ll post another update following Google’s next scheduled communication at 2:00 PM PDT or sooner if we detect full recovery.
Jun 12, 13:20 PDT
Update - Google has confirmed that their engineers have identified the root cause of the disruption and have applied mitigations. While most regions have stabilized, us-central1 remains partially impacted, and some Google Cloud products continue to experience degraded performance.

From Google’s update:

“Our engineers have identified the root cause and have applied appropriate mitigations.

While our engineers have confirmed that the underlying dependency is recovered in all locations except us-central1, we are aware that customers are still experiencing varying degrees of impact on individual google cloud products. All the respective engineering teams are actively engaged and working on service recovery.

We do not have an ETA for full service recovery.

We will provide an update by Thursday, 2025-06-12 13:30 PDT with current details.”

You can view the full update on the Google Workspace Status Dashboard:
https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW

We will continue monitoring the situation and provide our next update after Google’s next scheduled post at 1:30 PM PDT.

Thank you for your patience and understanding.
Jun 12, 12:55 PDT
Monitoring - Google has posted an update indicating that their Cloud & Workspace services have fully recovered in all regions except us-central1, which is now mostly recovered. However, they have not yet provided an ETA for full restoration in that region.

You can view the latest status directly from Google here:
https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW

What this means for Nylas customers:
• Users should start to see improved performance and fewer errors.
• Customers with mailboxes or resources hosted in us-central1 may still experience occasional delays or failures when accessing Gmail, Calendar, or Contacts via the Nylas API.

We will continue monitoring closely and will post another update after Google’s next scheduled communication, expected by Thursday, June 12 at 1:00 PM PDT.

Thank you for your continued patience.
Jun 12, 12:41 PDT
Update - Google has updated their Workspace status page as well. You can track their progress here:

https://www.google.com/appsstatus/dashboard/
Jun 12, 12:14 PDT
Update - We have confirmed that Google has officially reported issues with its cloud and Workspace services. You can view the incident details and affected components on Google's own Status Dashboards:

https://status.cloud.google.com/

At this time:
• Google is confirming a service disruption with elevated error rates and latency across Workspace APIs.
• The root cause appears to originate upstream in Google's infrastructure.
• Nylas remains fully dependent on Google's services for Gmail, Calendar, and Contacts integrations, and we are closely monitoring both Google’s dashboard and our own telemetry.

Impact:
Users may experience failed requests or timeouts when performing actions like sending emails, syncing calendars, or fetching contacts.

Next Steps:
• We are evaluating possible mitigations (e.g., request retries, timeouts adjustments).
• Engineers are actively monitoring resolution progress via Google's dashboard.

We will provide a follow-up update within 30 minutes or as further information becomes available.
Jun 12, 11:55 PDT
Update - We are continuing to investigate this issue.
Jun 12, 11:50 PDT
Update - We’ve identified that the elevated errors and latency affecting Google Workspace API appear to be part of a broader internet-wide disruption. Multiple cloud and SaaS providers are reporting similar issues, and the root cause may involve upstream networking or infrastructure providers.

Our team is continuing to monitor the situation closely and assess the impact on Nylas services. While this is external to our infrastructure, we are actively evaluating potential mitigations and will keep this page updated as we learn more.

Thank you for your continued patience.
Jun 12, 11:48 PDT
Investigating - We’re currently experiencing service degradation due to an ongoing issue with Google, which appears to be system-wide including GCP and Workspace accounts.

This is causing high latencies and error rates, and impacting the delivery all of Google services.

We’re actively monitoring updates from Google and will provide more information as it becomes available.
Jun 12, 11:34 PDT
Jun 11, 2025

No incidents reported.

Jun 10, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage