Disclosurely
Disclosurely →

System Health & Status Monitoring

Real-time platform uptime monitoring, performance metrics, incident reporting, and service status updates. Track system health, scheduled maintenance, and historical performance.

Monitor Disclosurely's platform health with real-time uptime tracking, performance metrics, incident reporting, and service status updates, so you can see whether your whistleblowing channel is available.

Overview

System reliability is critical for whistleblowing platforms. Reporters must have confidence that they can submit reports at any time, and organizations need assurance that their compliance infrastructure is operational 24/7. Disclosurely provides comprehensive system health monitoring with transparent status reporting.

Key Features:

  • Real-time uptime monitoring
  • Performance metrics dashboard
  • Incident notifications
  • Scheduled maintenance windows
  • Historical uptime reports
  • Regional status monitoring

Access: status.disclosurely.com (public) or Dashboard > System Health (authenticated)

Service levels: Service levels are not part of Pro. An SLA is available by agreement as part of an Enterprise contract; its terms, including any availability commitment or remedies, are agreed individually in that contract.

Status Page

Public Status Page

Real-Time System Status:

Access: https://status.disclosurely.com

Always Available:

  • No login required
  • Accessible even during incidents
  • Mobile-responsive
  • Multiple CDN nodes for reliability

Status Overview:

Service Components:

1. Reporting Portal

  • ✅ Operational
  • ⚠️ Degraded Performance
  • ⏸️ Partial Outage
  • 🔴 Major Outage

2. Dashboard (Admin Interface)

  • Status indicator
  • Response time (ms)
  • Last updated timestamp

3. Secure Messaging

  • Messaging service status
  • Notification delivery
  • Real-time sync status

4. File Uploads

  • Upload service status
  • Storage availability
  • Processing queue status

5. Email Notifications

  • Email delivery status
  • Queue length
  • Delivery rate

6. API Services (Enterprise)

  • API endpoint status
  • Rate limit status
  • Response times

7. Database

  • Primary database status
  • Replica status
  • Backup system status

8. Search & Analytics

  • Search service status
  • Analytics processing
  • Report generation

Overall Status:

System-Wide Indicator:

  • 🟢 All Systems Operational - Everything running normally
  • 🟡 Degraded Performance - System slower than usual but functional
  • 🟠 Partial Outage - Some services unavailable
  • 🔴 Major Outage - Critical services down

Current Incidents

Active Incidents:

When issues occur, incidents are posted in real-time:

Incident Information:

  • Title: Brief description (e.g., "Slow dashboard loading")
  • Status: Investigating, Identified, Monitoring, Resolved
  • Severity: Minor, Major, Critical
  • Affected Services: Which components impacted
  • Started: Time incident began
  • Updates: Chronological updates as situation evolves

Example Incident:

🟠 Slow File Upload Processing
Status: Monitoring
Severity: Major
Affected: File Uploads
Started: 2025-01-15 14:30 UTC

Updates:
[15:45 UTC] Resolved - Upload processing returned to normal.
            Monitoring continues for 1 hour.
[15:20 UTC] Identified - High load on processing servers.
            Scaling up capacity.
[14:45 UTC] Investigating - Reports of slow upload processing.
            Team investigating cause.

Incident Transparency:

All incidents are publicly disclosed:

  • Root cause analysis published (post-resolution)
  • Impact duration clearly stated
  • Affected user count (anonymized)
  • Remediation steps taken
  • Preventive measures implemented

Scheduled Maintenance

Planned Downtime:

Maintenance windows scheduled and communicated in advance:

Maintenance Notice:

  • Date & Time: Exact start time (UTC and local time zones)
  • Duration: Expected maintenance window
  • Affected Services: What will be unavailable
  • Impact: How users will be affected
  • Alternative Access: Workarounds if any

Example:

🔧 Scheduled Maintenance: Database Upgrades
Date: Sunday, January 28, 2025
Time: 02:00 - 04:00 UTC (10:00 PM - 12:00 AM EST)
Duration: ~2 hours
Affected: All services briefly (5-minute window)
Impact: Brief interruption during final cutover
Status: Scheduled

Advance Notice:

  • Minor Maintenance: 7 days advance notice
  • Major Maintenance: 14 days advance notice
  • Emergency Maintenance: As much notice as possible (minimum 2 hours)

Maintenance Schedule:

Maintenance typically scheduled during:

  • Weekend hours (Saturday/Sunday)
  • Late night (02:00-05:00 UTC)
  • Low-traffic periods
  • Regional off-peak hours

Performance Metrics

Response Time Monitoring

Real-Time Performance:

Access: Status page > Performance Metrics

Metrics Displayed:

1. Page Load Times

  • Reporting portal homepage: Target <2 seconds
  • Dashboard load: Target <3 seconds
  • Report submission: Target <1 second per page

2. API Response Times (Enterprise)

  • Average response time: Target <200ms
  • 95th percentile: Target <500ms
  • 99th percentile: Target <1000ms

3. Database Query Performance

  • Average query time: Target <50ms
  • Slow query count: Target <0.1% of queries

4. File Upload Speed

  • Average upload speed: Varies by connection
  • Processing time: Target <30 seconds
  • Thumbnail generation: Target <10 seconds

Performance Visualization:

Graphs Available:

  • Last 24 hours (real-time updates)
  • Last 7 days (daily averages)
  • Last 30 days (weekly trends)
  • Last 90 days (monthly trends)

Color Coding:

  • 🟢 Green: Normal performance
  • 🟡 Yellow: Slower than average but acceptable
  • 🟠 Orange: Degraded performance
  • 🔴 Red: Unacceptable performance

Uptime Percentage

Uptime Tracking:

Current Month:

  • Percentage uptime (99.X%)
  • Downtime minutes
  • Number of incidents
  • Mean time to resolution (MTTR)

Last 90 Days:

  • Uptime by month
  • Trend analysis
  • Incident frequency
  • Performance comparison

Historical Uptime:

Access: Status page > Uptime History

Availability commitments: We use commercially reasonable efforts to keep the Service available but do not guarantee uninterrupted access (see our Terms of Service). An SLA, including any availability commitment, is available by agreement as part of an Enterprise contract.

Learn More: Subscription Tiers

Incident Management

Incident Classification

Severity Levels:

Critical (P0):

  • Complete service outage
  • Data security breach
  • Data loss risk
  • All users affected

Response:

  • Immediate all-hands response
  • Updates every 30 minutes
  • Executive notification
  • Postmortem required

Major (P1):

  • Significant functionality unavailable
  • Many users affected
  • Core features degraded
  • Workaround available but difficult

Response:

  • Rapid response team engaged
  • Updates every hour
  • Senior engineering involved
  • Postmortem recommended

Minor (P2):

  • Limited functionality impact
  • Small user subset affected
  • Non-critical features affected
  • Easy workaround available

Response:

  • Standard response procedures
  • Updates as needed
  • Resolution during business hours
  • Internal review

Maintenance (P3):

  • Scheduled or planned work
  • Minimal user impact
  • Communicated in advance
  • Brief interruptions only

Response:

  • Standard change management
  • Advance communication
  • Rollback plan ready

Communication During Incidents

Notification Channels:

1. Status Page Updates

  • Real-time incident updates
  • Chronological timeline
  • Resolution status

2. Email Notifications (Subscribed Users)

  • Incident detected
  • Major updates
  • Resolution confirmation
  • Postmortem publication

3. In-App Banners

  • Active incident notification
  • Link to status page
  • Expected resolution time

4. Social Media (Major Incidents)

  • Twitter: @DisclosurelyStatus
  • LinkedIn: Company page updates

5. Direct Contact (Enterprise only, subject to scoping and agreement)

  • Dedicated account manager notification
  • Phone call for critical incidents
  • Slack/Teams integration

Subscribe to Notifications:

How to Subscribe:

  1. Visit status.disclosurely.com
  2. Click "Subscribe to Updates"
  3. Enter email address
  4. Select notification preferences:
    • All incidents
    • Major and critical only
    • Scheduled maintenance only
    • Specific service subscriptions
  5. Confirm subscription

Incident Postmortems

Transparency Reports:

After major incidents, detailed postmortems published:

Postmortem Contents:

1. Incident Summary

  • What happened
  • When it occurred
  • Duration of impact
  • Number of users affected

2. Timeline

  • Detection time
  • Response milestones
  • Resolution time
  • Communication timeline

3. Root Cause Analysis

  • Technical cause identified
  • Contributing factors
  • Why it wasn't prevented

4. Impact Assessment

  • Services affected
  • User experience impact
  • Data integrity confirmation

5. Remediation

  • Immediate fixes applied
  • Long-term improvements planned
  • Process changes implemented
  • Additional monitoring added

6. Lessons Learned

  • What went well
  • What could be improved
  • Action items with owners
  • Timeline for implementation

Example:

View past postmortems: status.disclosurely.com/postmortems

Hosting and Data Location

Disclosurely runs as a single production environment. Core case data is stored in our Supabase production project in the EU, and customers cannot choose a hosting region. The web application is delivered through Vercel.

Supporting services, such as email delivery and billing, are listed in the Supporting Services section of our Security Centre.

Backups and Recovery

The production database runs on Supabase's managed platform. Disclosurely does not currently offer backup restoration, automatic failover, multi-region replication, point-in-time recovery or recovery-time commitments.

Service Level Agreements (SLA)

Service levels are not part of Pro. An SLA is available by agreement as part of an Enterprise contract; its terms, including any availability commitment or remedies, are agreed individually in that contract.

Pro is provided on a commercially reasonable efforts basis, as described in our Terms of Service, and does not include an SLA, uptime guarantee or service credits.

If your organisation needs a contractual service level, contact us to discuss an Enterprise agreement. Any SLA is subject to scoping and agreement.

Health Monitoring Dashboard

Internal Health Dashboard

For Administrators:

Access: Dashboard > System Health (authenticated users only)

Organization-Specific Metrics:

1. Your Reporting Portal Status

  • Custom domain health
  • SSL certificate status
  • Link availability
  • Form submission success rate

2. File Upload Performance

  • Average upload speed (your organization)
  • Failed uploads count
  • Storage usage and limits
  • Processing queue for your files

3. Email Delivery

  • Notification delivery rate
  • Bounce rate
  • Email queue status
  • Failed deliveries

4. API Usage (Enterprise)

  • API calls per day
  • Rate limit status
  • Error rate
  • Endpoint performance

5. Integration Health

  • Email-code authentication success rate
  • Third-party integration status

Custom Alerts:

Set Up Alerts:

Configure notifications for your organization:

Alert Conditions:

  • Report submission failures
  • Email delivery failures
  • Storage capacity warnings
  • API rate limit approaching
  • Custom domain SSL expiration
  • Unusual activity patterns

Notification Methods:

  • Email to administrators
  • In-app notifications
  • Slack/Teams integration (Enterprise)
  • SMS alerts (Enterprise, critical only)

Access: Dashboard > Settings > Alerts

Diagnostic Tools

Self-Service Diagnostics:

Access: Dashboard > System Health > Diagnostics

Available Tools:

1. Connection Test

  • Test connection to Disclosurely servers
  • Measure latency
  • Check firewall/proxy issues
  • DNS resolution check

2. Email Deliverability Test

  • Send test notification
  • Verify email receiving
  • Check spam folder
  • SPF/DKIM verification

3. File Upload Test

  • Test file upload functionality
  • Measure upload speed
  • Verify processing
  • Check browser compatibility

4. API Health Check (Enterprise)

  • Test API authentication
  • Verify endpoint access
  • Check rate limits
  • Sample request/response

5. Custom Domain Test

  • Verify DNS configuration
  • Check SSL certificate
  • Test routing
  • Validate CNAME records

Test Results:

Each test provides:

  • ✅ Pass/❌ Fail status
  • Detailed error messages if failed
  • Recommendations for fixes
  • Support contact if assistance needed

Monitoring Best Practices

For Organizations

✅ Subscribe to Status Updates:

  • Monitor platform status proactively
  • Receive incident notifications
  • Plan around scheduled maintenance

✅ Monitor Your Metrics:

  • Review internal health dashboard weekly
  • Track report submission success rate
  • Monitor email delivery rate
  • Watch storage usage trends

✅ Set Up Alerts:

  • Configure critical alerts
  • Ensure multiple administrators notified
  • Test alert delivery quarterly
  • Review alert history

✅ Review Service Availability:

  • Check the status page after any reported issue
  • Escalate concerns early through support

✅ Test Integrations:

  • Verify webhooks delivering
  • Test email-code authentication monthly
  • Check API access regularly
  • Validate email routing

For Reporters

✅ Check Status Before Reporting:

  • Visit status page if experiencing issues
  • Verify it's not a known incident
  • Check scheduled maintenance calendar

✅ Understand Incident Status:

  • "Investigating" = Team aware, working on it
  • "Identified" = Root cause known
  • "Monitoring" = Fix applied, watching for stability
  • "Resolved" = Issue fully resolved

✅ Use Alternative Channels:

  • If online reporting unavailable, check for:
    • Phone hotline (if configured)
    • Email reporting (if configured)
    • In-person reporting (if available)

Historical Performance

Performance Reports

Monthly Performance Reports:

Access: status.disclosurely.com/reports

Report Contents:

Uptime Summary:

  • Overall uptime percentage
  • Uptime by service
  • Downtime breakdown
  • Incident count and severity

Performance Metrics:

  • Average response times
  • Performance compared to targets
  • Improvement trends
  • Regional performance

Incident Analysis:

  • Number of incidents
  • Mean time to detection (MTTD)
  • Mean time to resolution (MTTR)
  • Repeat incidents

Maintenance Summary:

  • Scheduled maintenance windows
  • Maintenance impact
  • Upgrades and improvements
  • Upcoming planned work

Customer Impact:

  • User-reported issues
  • Support ticket volume
  • Feature requests
  • Satisfaction metrics

Transparency Commitment

Our Commitment:

Always Public:

  • Real-time status information
  • Honest incident reporting
  • Detailed postmortems
  • Historical performance data

Never Hidden:

  • Minor incidents disclosed
  • Performance degradation reported
  • Maintenance impact communicated
  • SLA breaches acknowledged

Continuous Improvement:

  • Regular infrastructure upgrades
  • Proactive monitoring enhancements
  • Incident prevention focus
  • Performance optimization

Third-Party Dependencies

External Service Status

Services We Rely On:

Disclosurely depends on third-party services, including:

  • Supabase - Database, authentication, file storage and server-side functions
  • Vercel - Web application hosting and delivery
  • Resend - Email delivery
  • Stripe - Billing
  • Sentry - Error monitoring

SSO is planned; no Enterprise identity-provider integration is currently offered.

Each provider publishes its own service status.

Impact Handling:

When third-party outages occur:

  • Status page updated immediately
  • Incident attributed to third-party
  • Mitigation steps communicated
  • Alternative services activated when possible

Support During Incidents

Getting Help

During Active Incidents:

1. Check Status Page First

  • Verify if known incident
  • Review posted updates
  • Check estimated resolution

2. If Not Listed:

3. Urgent/Critical Issues:

  • Pro/Enterprise: Priority support line
  • Enterprise: Dedicated account manager
  • Include "URGENT" in email subject
  • Follow up with phone call if critical

Response Times:

Status Page Updates:

  • Critical incidents: Every 30 minutes
  • Major incidents: Every hour
  • Minor incidents: As needed
  • Maintenance: Before, during, after

Support Tickets:

  • Critical issues: <1 hour response
  • High priority: <4 hours response
  • Normal priority: <24 hours response
  • Low priority: <48 hours response

Enterprise Support (subject to scoping and agreement):

  • Dedicated Slack/Teams channel
  • Account manager direct line
  • Escalation procedures defined

Communicating with Reporters

During Platform Issues:

Best Practices:

✅ Inform Reporters Proactively:

  • Post notice on reporting portal (if accessible)
  • Send email to known reporters with active cases
  • Provide status page link
  • Offer alternative reporting methods

✅ Extend Deadlines:

  • If SLA timers affected by outage
  • Communicate extension clearly
  • Document in audit trail

✅ Preserve Trust:

  • Be transparent about issues
  • Apologize for inconvenience
  • Reassure about data security
  • Confirm no data loss

Audit Trail

System Events Logged:

All system health events recorded in audit trail:

  • Incident start/end times
  • Maintenance windows
  • Performance degradation
  • Failover events
  • SLA breaches

Learn More: Audit Trail

Notifications

System Health Notifications:

Integrated with notification system:

  • Incident alerts
  • Maintenance reminders
  • Performance warnings
  • SLA breach notifications

Learn More: Notification System

Security Monitoring

Security Incidents:

Security-related incidents handled separately:

  • Reported on status page
  • Detailed disclosure (after mitigation)
  • User notification if data affected
  • Regulatory reporting as required

Learn More: Security Overview

Support

Questions about system health?