Outagepilot · Daily Ships · Report sample-b
Google Workspace — 15 users, 9-hour outage — Nov 2026
Gmail: 98.75% uptime in Nov 2026 -> 7 days of service added. File by Wed 30 Dec 2026 (Google support case). 15 days needs 1,621 more minutes of downtime this month.
Consider waiting until Mon 30 Nov 2026 (month end) before filing: further downtime this month could move you to the next credit tier, and your deadline (Wed 30 Dec 2026) allows it. Third-party tactic — Office Watch: "Why not wait until November 30 to make a claim. If (heaven forbid) there’s more trouble, it might be possible to make a larger claim. [third-party tactic, Office Watch]"
| Service | Users | User-minutes | Downtime user-min | Uptime % | Tier | Credit | Fee | Credit amount | Eligible? |
|---|---|---|---|---|---|---|---|---|---|
| Gmail | 15 | 648,000 | 8,100 | 98.75% | < 99% → 7 days | 7 days | £88.50 | £0.00 | Yes |
Gmail: the next tier (below 95%) needs 1,621 more minutes of downtime this month.
Gmail: Fee shown is an example fee for illustration; replace it with the amount on your invoice.
Deadlines
- File your Google support case by: Wed 30 Dec 2026 (Google Workspace SLA)
Claim ticket — ready to paste
Subject: Google Workspace SLA service credit request — Nov 2026
I am the administrator for Northwind Surveyors. I am requesting a service credit under the Google Workspace Service Level Agreement.
Organisation: Northwind Surveyors
Tenant ID: {tenant_id}
Service affected (affected resource name): Gmail
- Incident ID: GW-EXAMPLE-9H (from the Service Health Dashboard)
1. Description of the incident: Our users were affected by incident GW-EXAMPLE-9H for Gmail. Description of errors that occurred during the incident: {describe_the_errors_users_saw}
2. Time and duration of downtime: 2026-11-10T09:00 to 2026-11-10T18:00 (UTC), 540 minutes. In UTC: 2026-11-10T09:00:00.000Z to 2026-11-10T18:00:00.000Z.
3. Number and location(s) of affected users: All 15 of our 15 licensed users, at {office_location}.
4. Our attempts to resolve the incident at the time: {describe_what_you_tried — e.g. checked Service Health, tested other clients/networks, raised ticket {support_ticket_number}}
Uptime calculation for Nov 2026:
Minutes in month: 43,200. Downtime: 540 minutes. Monthly Uptime Percentage: (43,200 − 540) / 43,200 × 100 = 98.75%.
I request 7 days of service added (or the monetary equivalent if billed monthly online) for Gmail.
Attached / available on request: {screenshots_error_messages_service_health_exports_and_PIR}
Contact: {your_name_role_and_email_on_this_tenant_domain}
Evidence checklist
- A detailed description of the Incident (SLA claim item i).
- Information regarding the time and duration of downtime (SLA claim item ii).
- Affected resource names — the services above (SLA claim item iii).
- The number and location(s) of affected users (SLA claim item iv).
- A description of errors that occurred during the incident (SLA claim item v).
- Tenant ID — replace {tenant_id} with your tenant GUID. Partner Center also requires: "Customer tenant ID and outage ID (from the Service Health Dashboard) must be provided."
- Incident IDs from Service Health: "You can find the identifier for the outage incident on the Service Health page in the Microsoft 365 admin center."
- Evidence that proves customer impact (screenshots, error messages, Service Health exports, the Post-Incident Review when published). Export it before the Service Health history window closes.
- Descriptions of your attempts to resolve the incident at the time of occurrence (Partner Center required information).
- Where to file (as written in research): direct customers — "admin center, Help & support | Contact Support" (third-party, Office Watch, https://office-watch.com/2026/microsoft-365-outage-sla-claim/); CSP customers — your provider creates the Partner Center support ticket ("Create a support ticket in Partner Center", official Partner Center guidance).
Next steps
- Mon 16 Nov 2026 — Today: save your evidence — screenshot or export the Service Health incident pages, user error messages and the times your users lost and regained the service (Service Health keeps about 30 days — third-party, Office Watch).
- Mon 16 Nov 2026 — Confirm the fee for each affected service from your invoice. If you buy a suite, confirm the share of the suite fee for each service — the SLA gives no fixed split, and credits are prorated to the affected service only.
- Mon 30 Nov 2026 — Wait until month end before filing if the next credit tier is within reach — more downtime this month counts towards the same claim (third-party tactic, Office Watch).
- Wed 30 Dec 2026 — Create the Google support case requesting the days of service added, within thirty days from the time you become eligible. Keep the case number.
- Wed 30 Dec 2026 — Check the next bill for the credit. Credits are applied to service fees (Microsoft) or as days added / a monetary equivalent (Google monthly online billing); they are not automatic and the provider decides every claim.