System Upgrade: August 16, 6:00 AM UTC
Maintenance Summary
On Saturday August 16 at 02:00 AM EDT (6:00 AM UTC), we will be performing an upgrade/migration of our web servers and databases to a Heroku Shield Private Space as part of upcoming PCI DSS Service Provider Attestation of Compliance (AoC):
During the upgrade/migration, the PixieBrix service will be offline for 5-10 minutes
We will be updating the DNS CNAME record for
app.pixiebrix.comIf you are using a custom domain pointed directly to our current Heroku host via CNAME record, you will need to update your DNS records. Our platform team will contact you with more information
We do not expect any additional service impact/downtime
We've chosen the maintenance window to minimize impact on operations across our customers. If you have concerns about the impact on your business operations, please email me your Account Executive.
Which features of PixieBrix will be offline during maintenance?
The Admin Console and API (app.pixiebrix.com) will be offline, which includes:
Account Management
Mod Deployments
Package Registry
Personal/Team Databases
Mod Telemetry
API Gateway
Mods already on a user's device that do not use the PixieBrix service will continue to operate as normal
How long is maintenance expected to take?
Our upgrade preparation/testing indicates the system will be offline for 5-10 minutes
How will my deployments/mods be impacted?
Mods already on a user's device that do not use the PixieBrix service will continue to operate as normal
To minimize impact on your operations, ensure your team members have received their mods prior to the maintenance window
For mods that require access to PixieBrix to function, consider temporarily pausing those deployments
If you have questions on how the maintenance will impact your mods, contact [email protected]
What infrastructure actions do I need to take?
In most cases, no action is required. See above: How will my deployments/mods be impacted?
If you are using a custom domain pointed directly to our current Heroku host via CNAME record, you will need to update your DNS records. Our platform team will contact you with more information
If you are manually overriding the Time to Live (TTL) for the
app.pixiebrix.comCNAME record, you will need to force a DNS refresh. We will be updating the CNAME record during the upgrade/migration and shortening the TTL leading up to the maintenance
Where can I receive maintenance schedule and status updates?
You can subscribe to our system status and maintenance calendar via Statuspage
Why are we upgrading/migrating to a Heroku Shield Private Space?
PixieBrix will be undergoing a PCI DSS SAQ-D audit in late August with A-LIGN
Heroku Shield Private Spaces offer Heroku's highest compliance guarantees
What disaster recovery and business continuity measures are in place?
A complete backup of customer data is being made prior to the upgrade
In the case of a problem during migration/upgrade, we'll rollback to the backup of the database
What will be the impact of users with the "enforceAuthentication" policy?
If the extension cannot retrieve the authentication/restricted URL policy on startup, the PixieBrix extension will not restrict access to pages
Last updated
Was this helpful?