Aurixa Systems
59A6F1AC81371 9B8365C5973688 F6A88E691AF668 B2181DFA30A52 67FABF99C7828 ECF7EE722A4DF 50279BB6551FC 5B4D9FCF3B68E8 86D37F1B72FD8 3D75E5C1D6D7F 2AFD2F22B7D048 2B076C791F5AA8 21194041C607D8 3C22606C7892A FF7887C48752F FA56B872187C9 76EA3AE7880FF 58818FA87A96F8 21C3441F51CCE F5177518AB0408 05AC85A2F1BDE 7D273D1B396BF8 3723709F51E8F8 B45725FCA69AE8 BE42347A6C4118 9A8017212A07 C14917CB164DA8 CD9F652CAC902 9FDA192618DB3 7F0C705A924AA8 0FBE5DDED089A8 570C484F7CBB2 3F229ECF214E2 95E9EDFB8E1EC FF0EAEAB8B11B8 DF87E36AC12AE8 5B3C50F76A1A88 AAF3165C91CF1 1BDF6FD420A36 D6F8BCCFA93BA8 5005413A45E908 94B2D8249ECD7 E9BD2A5A15A27 19BEEEC962441 560BB74C1017B BEFBF3E29D1B5 B73FF6BF9F8C88 05DC101830231 5E2FDFD998C018 89F223A403831 D22EDE0BE6937 39BFDEC4C61D6 381D4BA7187D58 F871E3F3A6EC98 39016BF2DB4758 3C58BDFA50AA98 90379F2ADC97 3E7129243CBBC8 DFCB9AE31AF78 7CFEDD3A883C28 31517F24C8D2F D03BED3B28D3F8 ED697818073508 FE75BB864E6068 12765C02D52C58 D8079C68081BD DD6B542E35E29 1AD948E6DD3EE8 37364C0884ECC EE2877878ECB2 B08A04D328A7D 0F92E0A261791 25F1B735D2199 C336AFD2ABDAF8 9AA8F2F8DF3298 F3ABAB546BB528 84049FDA0FE59 0412AAE77B4B38 F6A83AED7C9FB 90FB9EC482EF58 A348558A378558 452002ED27A0A DE956671FA846 4948CBA5FBC5A8 5E0D5593A1677 5A1BCE9ABCB63 AC74CD50C4A888 3DF91B972CC68 660549EF11AFC AAEC85E221F4F8 1EDB83A46453E8 2DBEE933136AD AC1C793EF2142 24C71D4ACB9B78 91B8C032C7C04 FC3D4A92859AE F1BD6F3871A6C8 8E788507F14CA 940ACFD79E345 B4E1D15D272D2

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.