Skip to main content

Server status?

Answered

Comments

2 comments

  • Blurams Support
    Thank you for your thoughtful, long-standing support—and especially for recommending blurams to others. It truly means a great deal to us.

    To address your question directly:
    There is currently no public-facing status page (e.g., status.blurams.com) where users can check real-time server health, ongoing maintenance, or incident reports. We understand how valuable such transparency would be—especially during brief, unexplained disconnections like the 20-minute offline event you and your friend experienced—and your suggestion aligns with industry best practices.

    That said, here’s what we *do* monitor and how it relates to your experience:

    🔹 Server-side monitoring: Our infrastructure team continuously monitors core services—including cloud recording ingestion, push notification delivery, device authentication, and live stream routing. Any confirmed outage or scheduled maintenance affecting multiple users is internally escalated and addressed within minutes.

    🔹 Why brief disconnections *can* occur without local cause:
    Even when your Wi-Fi, power, and device are fully stable, short-lived disruptions (e.g., ~10–30 minutes) may stem from:
    - Temporary load balancing across regional cloud nodes;
    - TLS certificate auto-renewal handshakes between device and server;
    - Brief DNS propagation delays after global configuration updates;
    - Network-level rate limiting triggered by unusually high concurrent reconnect attempts (e.g., during widespread ISP outages or firmware rollout waves).

    These are typically self-healing and require no user action—but they *are* logged on our end with timestamps, device MAC addresses, and error codes.

    🔹 What you can do right now to help isolate the cause:
    To determine whether this was isolated to the server—or potentially tied to your specific device, network, or account—we’d appreciate just a few quick details (no personal info needed):
    - Your device model (e.g., A31C, S21C, D10S, etc.);
    - Approximate time (including timezone) when the disconnection occurred;
    - Whether the camera reconnected automatically—or required manual intervention (e.g., power cycle, app refresh);
    - If other devices on the same account remained online during that period.

    This helps us cross-check against internal logs—not to troubleshoot *your* setup, but to verify whether it correlates with any known platform behavior.

    Finally, your point about log retention is well taken: all system logs are rotated weekly per security and compliance standards, and historical incident summaries (without PII) are retained internally for trend analysis—but not exposed publicly at this time.

    We’re actively evaluating the feasibility of a lightweight, read-only status dashboard for registered users in future releases—and your feedback strengthens that case.

    In the meantime, if you notice another brief disconnect—or anything that feels inconsistent with your usual reliability—please reply here with the four details above. We’ll look it up directly and let you know what, if anything, occurred server-side.

    Thanks again for your patience, trust, and constructive voice. It’s users like you who help us improve—not just technically, but thoughtfully.
    0
  • Carol.Lombard.Anderson

    I cannot connect to server, I reinstalled, my app still nothing, I rebooted my wifi still nothing. My app won't let me log in and no camera. It quit working around noon today. It is now 6pm. Pacific standard time. My camera is the A31S

    0

Please sign in to leave a comment.