Home
/
Status
/
Service
Globality down? Check the current Globality status right now, learn about outages, downtime, incidents, and issues.
Source
auto
Category
SaaS
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 2h ago
5
Components
0
Active incidents
0
Maintenance
25%
90d uptime
Degradation of project creation & invitation
May 27, 2:46 PM
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
Showing 1 to 5 of 5 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Platform availability | Operational | Component | Not recorded |
Project creation & invitation | Operational | Component | Not recorded |
Proposal creation & submission | Operational | Component | Not recorded |
APIs | Operational | Component | Not recorded |
3rd party integrations | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Related status pages based on category, adapter type, and operational history.
Globality is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
Normalized official status-page data for incidents, maintenance, components, and history.
25%
Known uptime
4 known history days
5
Components tracked
0 outage, 0 degraded
12
Incidents indexed
0 active right now
0
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
3rd party integrations
Operational
APIs
Operational
Platform availability
Operational
Project creation & invitation
Operational
Proposal creation & submission
Operational
1
operational days
0
degraded days
3
outage days
0
maintenance days
86
unknown days
Latest outages and degradations detected from the official status page.
On May 27, between 14:11 UTC and 16:29 UTC, Globality users experienced slowness stemming from underlying issues with a service provider's API. Once we identified the issue, we temporarily switched over to another vendor to mitigate. Based on this incident, we are optimizing our platform to handle such incidents in a shorter time.
On May 8, between 16:37 UTC and 23:55 UTC, Globality experienced platform impacts stemming from multiple high-volume operations. Based on this incident, we have optimized our platform to handle such operations without impacting overall platform performance.
This incident has been resolved. Globality has identified a performance issue during a routine service upgrade, we are implementing guardrails to ensure that future service upgrades do not impact performance.
Between March 18, 20:45 UTC and March 19, 1:09 UTC Globality experienced an incident with project creation, wherein the project brief was skipped entirely and users were taken directly to supplier matching with all brief sections empty. Based on this incident, we accelerated and completed the migration of the underlying service from legacy to newer, more robust infrastructure.
On March 11, between 21:30 UTC and 23:08 UTC Globality experienced an incident with project creation, wherein the project brief was skipped entirely and users were taken directly to supplier matching with all brief sections empty. Based on this incident, we will be migrating the underlying service from legacy to newer, more robust infrastructure.
Between January 30, 20:50 UTC and January 31, 00:13 UTC, some users on the Globality platform were experiencing performance issues due to a misconfiguration during a routine service upgrade.
On January 15, between 10:00 UTC and 17:00 UTC, users on the Globality platform were experiencing performance issues due to an inadvertent configuration change for multiple services. Based on this incident, we are implementing additional guardrails for configuration changes of this type to prevent future performance impact.
On October 20, between 8:11 UTC and 10:27 UTC, the Globality platform was down due to an AWS outage. https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_BA540_514A652BE1A
This incident has been resolved. Globality has identified an issue in the service delivery pipeline that resulted in this incident, and will implement improved monitoring and durability for the impacted pipeline.
On August 22, between 4:44 PM GMT and 5:53 PM GMT, Globality experienced a degradation with project invitations. Users may have experienced issues viewing provider information. We mitigated the issue and restored service for all users. Based on this incident, we are implementing enhanced alerting to detect similar issues even sooner and ensure continued reliability.
Scheduled and completed maintenance windows are separated from incidents.
No recent maintenance windows recorded.
Uptimus tracks the official Globality status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.globality.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
