Aurixa Systems
843812148F2C2 3D4308C9C1EF18 3A625D063236D B4F46567AA6668 878A5A12384A28 9A71C1521FCF7 FD2A89C1A238B A369118864D51 97B9F393F489A CBA13DFEE38B5 6634D274586448 DCF082E2CA777 CE5D24E932525 74A4C2CC12DB4 EAC9B6A0601BC8 6CE935E5081D08 89D4761FE96CA 8C1B16D24C4F28 ACF353527862B 79891EB2C296D8 FD94EE51DD922 63C019CFBB5638 CA1FB2A8961408 987006635FF3B 749D984DE40B28 C0EAB6580EBC38 D6CCBEC57795B 3DD22E57E85BD8 4F8A034929CCB A8B717B5DE0728 D2C2B26BFFAA4 64F96C3D19E9D8 78D81D9DC73198 C97B3BAAB48808 969DB04E7D9D3 4A95542AE7E03 A9C3C2EB96913 23093780BFA18 0B678F035A7E08 ACB09F09BC6778 A21DAE0B95DB8 2C646BF58900A 2D1CC05C729AF8 C18D7981EBA538 F563D633E43328 2E987A34ED9F98 84F724BE19CA98 E7F9A29B2D5208 D148A9648C3DF8 7A1BD699558C1 C4769ADE4B6128 EDC666A756EBC8 F46CC7BBB85E4 6F1152ED77FE3 AC929E6FDE8D38 58C91D369560B8 A7A8F4A7E61B88 76A8371393423 6AF5CB77EAC0B8 26561E7417D848 49296A0B1532A C1C6AF5D73D918 20A5255095488 0F4FBBDC5882D F0C505BE5F1988 D5310A55779798 1ACFB27E775EB 10F039BE1DCCD8 1546B63EF271C8 52E352AEABBFE 8C805F964B318 E403E474C10CB8 E4348B196E09 9A52AF34CB80F 6ADD8429773E2 B34C2C8786FF88 07A3B3BC64EFE8 8C16A871F2DA78 F47BDCFF9D059 B40EFD98C76A38 D1E135232868A A1D7838870F3E D837955002379 F2A9BD16932E1 A590CB1E1DEC5 011FCAAC4D2E2 DE5536F5B4CA 39AB75CDC3CC08 7C616F373EBFF8 558EAC2089284 59A5F4E0944628 C24C279CCEF2B8 9BA52E0099617 28BC5AE2AAFF58 B43D700E48BAD 9403481104592 E5CAF98BE9A358 3ED37A9E35E7B D1A0861572D1 7D42C12462944

Aurixa System Status

System status.

The live health of every service Aurixa Systems runs on, polled directly from each provider’s official status feed every five minutes. Providers are shown by role rather than by name. Each card says what it does for us and which features an incident there can touch.

Fetching live status…

Live · polled every 5 min

Service health

  • Backend platform

    Runs our databases, sign-in and application APIs. An incident here can affect logging in, loading dashboards and saving changes.

    Can affectSign-inDashboardsData & APIs

  • Edge security & delivery

    Sits in front of every request we serve: DNS, traffic protection and content delivery. An incident here can make our sites slow or unreachable.

    Can affectSite reachabilityLoad times

  • Web hosting

    Serves this website and the customer-facing portals. An incident here can stop pages loading.

    Can affectWebsiteCustomer portals

  • Code & release pipeline

    Hosts our source code and powers releases. An incident here can delay fixes and updates, but never touches the running product.

    Can affectRelease cadence only

  • AI models

    Runs the models behind AI features such as the Support Portal's screening assistant. An incident here can make AI answers slow or unavailable while everything else keeps working.

    Can affectSupport assistantAI features

  • Payments

    Processes card payments and subscription billing. An incident here can affect checkout and plan changes; active services keep running.

    Can affectCheckoutBilling

  • Email delivery

    Sends our transactional email: receipts, invitations and notifications.

    Can affectEmail notifications
Something broken for you specifically? → Raise a support ticket

Every state on this page is live: our servers poll each provider’s official status feed every five minutes and keep the history you see here. Days before our own polling began are reconstructed from each provider’s published incident record, and re-synced daily. Nothing is entered by hand, and nothing is cached for more than a minute.