Previous incidents
store.profitbase.com is down
Resolved May 6, 2025 at 4:16am UTC
store.profitbase.com recovered.
1 previous update
store.profitbase.com is down
Resolved May 4, 2025 at 4:15am UTC
store.profitbase.com recovered.
1 previous update
app1.profitbase.biz is down
Resolved May 2, 2025 at 10:01pm UTC
app1.profitbase.biz recovered.
1 previous update
store.profitbase.com is down
Resolved Apr 30, 2025 at 4:11am UTC
store.profitbase.com recovered.
1 previous update
store.profitbase.com is down
Resolved Apr 24, 2025 at 11:43am UTC
store.profitbase.com recovered.
1 previous update
store.profitbase.com is down
Resolved Apr 21, 2025 at 12:06pm UTC
store.profitbase.com recovered.
1 previous update
store.profitbase.com is down
Resolved Apr 1, 2025 at 2:18pm UTC
store.profitbase.com recovered.
1 previous update
app1.profitbase.biz is down
Resolved Mar 26, 2025 at 8:52pm UTC
app1.profitbase.biz recovered.
The cluster failed to schedule new nodes. Seems something on the Azure side either got locked up or unavailable for 20 minutes. No changes done on our side, but suddenly able to allocate new nodes again.
1 previous update
profitbase.biz and app1.profitbase.biz are down
Resolved Mar 22, 2025 at 1:41am UTC
app1.profitbase.biz recovered.
3 previous updates
connect-microsoft.profitbase.com and store.profitbase.com are down
Resolved Mar 17, 2025 at 9:43pm UTC
store.profitbase.com recovered.
3 previous updates
connect-microsoft.profitbase.com is down
Resolved Mar 17, 2025 at 8:47pm UTC
connect-microsoft.profitbase.com recovered. Site was unavailable for roughly 7 minutes in total. Not sure why this keeps happening, but it's not related to any updates we're applying, so it must be related to the underlying azure service. As this isn't a critical service for Profitbase Flow to function we're investigating if we should make the outage threshold higher to get fewer of these messages.
1 previous update
profitbase.biz degraded
Resolved Mar 4, 2025 at 2:40pm UTC
profitbase.biz recovered.
1 previous update