Documentation Index
Fetch the complete documentation index at: https://neuroai-cf1c4abf.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
What is the Neuro AI Status Page?
The Neuro AI Status Page (in Neuro Settings) is your real-time dashboard for:
- System Status — Current health of all Neuro services
- Performance Metrics — Response times, uptime, availability
- Incident Reports — Real-time updates on any issues
- Maintenance Notifications — Scheduled downtime and updates
- Service History — Past incidents and resolutions
- API Status — Integration and automation availability
- Component Status — Individual service status checks
Part 1: Understanding System Status
Status Indicators
Each Neuro component displays one of these statuses:
🟢 OPERATIONAL
- Service is fully functional
- All features available
- Normal performance
- No known issues
🟡 DEGRADED PERFORMANCE
- Service is available but slower than normal
- Some features may be affected
- Performance is below standard
- User action may be delayed
🔴 PARTIAL OUTAGE
- Some users cannot access service
- Specific features unavailable
- Alternative features available
- Team is investigating
🔴 MAJOR OUTAGE
- Service completely unavailable
- All users affected
- Team working on immediate restoration
- Regular updates provided
⚪ MAINTENANCE
- Scheduled maintenance in progress
- Service temporarily unavailable
- Expected duration provided
- Advance notification given
Part 2: Key Services & Components
Core Neuro Services
1. Super Agent Service
Description: The autonomous AI agent that handles all tasks Status Check: Can Neuro accept and process requests? Typical Response Time: 2-5 seconds Uptime Target: 99.9%
What to do if down:
- Check status page for updates
- Wait for team notification
- Do not submit critical tasks
- Contact support if urgent
2. Research & Web Search Service
Description: Real-time web research and information gathering Status Check: Can Neuro search the web? Typical Response Time: 3-8 seconds Uptime Target: 99.5%
What to do if down:
- Pre-loaded knowledge still available
- External research temporarily unavailable
- Offline tasks can continue
- Check for estimated resolution time
3. Content Creation & Generation Service
Description: Document, presentation, and image generation Status Check: Can Neuro create files and documents? Typical Response Time: 5-15 seconds Uptime Target: 99.8%
What to do if down:
- Chat with Neuro still works
- File creation unavailable
- Wait for restoration
- Alternative: manual document creation
4. Code Execution & Development Service
Description: Code generation, execution, and deployment Status Check: Can Neuro write and run code? Typical Response Time: 5-20 seconds Uptime Target: 99.5%
What to do if down:
- Chat-based analysis still available
- Code execution unavailable
- Use local development environment
- Restoration in progress
5. App Integration & Automation Service
Description: Connection to 700+ external applications Status Check: Can Neuro access your connected apps? Typical Response Time: 2-8 seconds Uptime Target: 99.7%
What to do if down:
- Check which apps are affected
- Some integrations may work, others may not
- Use app directly for urgent needs
- Team investigating cause
6. Image & Visual Generation Service
Description: AI image generation (DALL-E, Midjourney, etc.) Status Check: Can Neuro generate images? Typical Response Time: 10-30 seconds Uptime Target: 98.0% (depends on third-party services)
What to do if down:
- May be third-party service issue
- Check Neuro status page
- Use local design tools as backup
- Team working on resolution
7. Voice & Audio Service
Description: Voice AI, phone calling, speech recognition Status Check: Can Neuro make calls or process audio? Typical Response Time: 2-5 seconds Uptime Target: 99.5%
What to do if down:
- Text-based interactions still work
- Voice features temporarily unavailable
- Schedule calls for later
- Check for updates
8. Database & Storage Service
Description: Data storage, retrieval, and management Status Check: Can Neuro access your data? Typical Response Time: 1-3 seconds Uptime Target: 99.95%
What to do if down:
- Most critical service
- Cannot access saved data
- Do not submit new data
- Contact support immediately
Part 3: Reading the Status Page
Status Dashboard Overview
The status page displays:
STATUS SUMMARY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Overall System Status: [OPERATIONAL / DEGRADED / OUTAGE]
Last Updated: [Time]
Incident Count: [Number of active incidents]
ACTIVE INCIDENTS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[If any incidents exist, they're listed with updates]
SYSTEM COMPONENTS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🟢 Super Agent Service — Operational
🟢 Research Service — Operational
🟢 Content Generation — Operational
🟢 Code Execution — Operational
🟢 App Integration — Operational
🟡 Image Generation — Degraded (slow)
🟢 Voice Service — Operational
🟢 Database & Storage — Operational
PERFORMANCE METRICS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
API Response Time: 234ms (Normal: 200ms)
Uptime (30 days): 99.87%
Success Rate: 99.92%
Active Users: 45,230
SCHEDULED MAINTENANCE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Next maintenance: [Date/Time]
Expected duration: [Minutes]
Affected services: [List]
Part 4: Incident Management
What is an Incident?
An incident is any event that reduces service availability or performance:
- Service outage (complete unavailability)
- Degraded performance (slower than normal)
- Intermittent issues (working on and off)
- Feature unavailability (specific function down)
- Third-party service issues (dependencies)
Incident Severity Levels
Critical (🔴)
- Impact: Service completely unavailable
- Duration: Usually minutes to hours
- User Impact: All users affected
- Response: Immediate
- Example: Database down, Super Agent not responding
Major (🔴)
- Impact: Significant functionality unavailable
- Duration: Usually 15-60 minutes
- User Impact: Many users affected
- Response: Urgent (minutes)
- Example: Research service down, Code execution failing
Minor (🟡)
- Impact: Non-critical features unavailable
- Duration: Usually 5-30 minutes
- User Impact: Some users affected
- Response: Soon (minutes to hours)
- Example: Image generation slow, App sync delayed
- Impact: No functional impact
- Duration: N/A
- User Impact: None
- Response: Informational
- Example: Maintenance scheduled, Performance update
During an Incident
WHAT TO DO:
1. Check the Status Page
- See what's affected
- Read latest update
- Note estimated resolution time
2. Review Incident Details
- What service is affected?
- What started the incident?
- What's the team working on?
3. Use Available Services
- Use services that ARE operational
- Avoid the affected service
- Don't repeatedly retry
4. Subscribe to Updates
- Get real-time notifications
- Receive via email/SMS
- Know when service returns
5. Contact Support if Needed
- For business-critical issues
- For workaround suggestions
- For ETA clarification
Uptime Percentage
Uptime = (Total Time - Downtime) / Total Time × 100
Target: 99.9% (allows ~7 hours downtime per month)
99.9% = ~44 minutes downtime per month
99.5% = ~3.6 hours downtime per month
99.0% = ~7.2 hours downtime per month
Response Time
How long it takes Neuro to respond to requests
Optimal: 200-500ms
Acceptable: 500ms-2 seconds
Degraded: 2-10 seconds
Poor: 10+ seconds
Factors affecting response time:
- Request complexity
- System load
- Available resources
- Network conditions
Success Rate
Percentage of requests that complete successfully
Target: 99.9%
Good: 99.0-99.9%
Acceptable: 95-99%
Poor: <95%
API Rate Limits
Number of requests allowed per time period
Standard: 100 requests per minute
Premium: 500 requests per minute
Enterprise: Custom limits
Exceeding limits: Temporary throttling
Part 6: Maintenance & Scheduled Downtime
Types of Maintenance
Planned Maintenance
ADVANCE NOTICE
- Announced 7-14 days ahead
- Specific date/time provided
- Expected duration listed
- Services affected identified
PURPOSE
- System updates and patches
- Performance improvements
- Security enhancements
- Infrastructure upgrades
DURING MAINTENANCE
- Service unavailable
- Existing tasks may be paused
- New requests not accepted
- Updates applied
AFTER MAINTENANCE
- Services restored
- Performance may improve
- New features available
Emergency Maintenance
NOTICE
- May have no advance notice
- Critical security or stability issues
- Minimal time to prevent major problems
DURATION
- Usually 15-60 minutes
- Occasionally longer if severe
COMMUNICATION
- Real-time updates on status page
- Email and SMS alerts
- Team working to minimize impact
Maintenance Windows
Typical maintenance schedule:
SCHEDULED WINDOW
- Day: Usually Tuesday-Thursday
- Time: 2:00 AM - 6:00 AM UTC
- Duration: 15-60 minutes
- Frequency: Monthly or as needed
AVOID HIGH-LOAD TIMES
- Off-peak hours selected
- Minimal user impact
- Planning allows preparation
PREPARE FOR MAINTENANCE
- Complete critical tasks before window
- Don't schedule tasks for maintenance time
- Have offline backup if needed
- Review status page for details
Part 7: Troubleshooting Guide
Service is Slow
Symptoms:
- Requests taking longer than usual
- Timeouts occurring
- Responses delayed
Possible Causes:
- High system load
- Network latency
- Service degradation
- Large request size
What to Do:
1. Check Status Page
- Is service showing degraded status?
- Are others affected?
- What's the team saying?
2. Check Your Connection
- Test internet speed
- Try different network
- Restart your device
3. Simplify Your Request
- Reduce scope of task
- Use less data
- Break into smaller requests
4. Try Again Later
- Load may be temporary
- Wait 5-10 minutes
- Retry with fresh session
5. Contact Support
- If persistent
- For urgent needs
- For enterprise SLA support
Service is Down
Symptoms:
- Cannot access Neuro
- Getting error messages
- All requests fail
Possible Causes:
- Complete service outage
- Regional connectivity issue
- Account/authentication issue
- Third-party dependency down
What to Do:
1. Check Status Page
- Is service marked as down?
- What's the incident update?
- What's estimated resolution?
2. Check Your Account
- Can you log in?
- Is subscription active?
- Are there any account issues?
3. Check Your Connection
- Can you access other sites?
- Is your internet working?
- Try different network/device
4. Wait for Resolution
- Team is working on it
- Check status page for updates
- Don't repeatedly retry
5. Contact Support
- For business-critical needs
- For workarounds
- For SLA claims
Some Features Not Working
Symptoms:
- Specific feature failing
- Other features work fine
- Partial functionality
Possible Causes:
- Feature-specific service down
- Configuration issue
- Integration problem
- User permission issue
What to Do:
1. Check Status Page
- Is that specific service listed as down?
- What's the status?
- What's the team update?
2. Check Your Settings
- Is the feature enabled?
- Are permissions correct?
- Is configuration proper?
3. Try Alternative Method
- Use different approach
- Access feature differently
- Use related feature
4. Wait for Resolution
- If service is down
- Check for updates
- Team working on fix
5. Contact Support
- For configuration help
- For persistent issues
- For feature questions
Integration Not Working
Symptoms:
- Connected app not syncing
- Actions not executing
- Data not transferring
Possible Causes:
- Integration service down
- Third-party service down
- Authentication expired
- Permission issue
What to Do:
1. Check Status Page
- Is App Integration service operational?
- Is third-party service listed as issue?
2. Check Integration Settings
- Are credentials current?
- Are permissions granted?
- Is integration enabled?
3. Re-authenticate
- Reconnect to third-party app
- Grant permissions again
- Verify credentials
4. Test Basic Functionality
- Use app directly
- Confirm it's working
- Test action manually
5. Contact Support
- For persistent issues
- For configuration help
- For third-party coordination
Part 8: Notification & Alert Settings
Subscribe to Status Updates
Email Notifications:
How to Enable:
1. Go to Status Page (https://www.neuro-agent.ru/status)
2. Look for "Subscribe" button
3. Enter your email
4. Confirm subscription
You'll Receive:
- Incident notifications (immediate)
- Incident updates (major changes)
- Resolution notifications (service restored)
- Maintenance announcements (7+ days before)
Frequency:
- Only when events occur
- Not spam, only important updates
- Can customize notification preferences
How to Enable:
1. Account Settings
2. Notifications
3. Add phone number
4. Verify with code
Benefits:
- Instant alerts
- No email delay
- Critical incidents only
- Mobile-friendly
For Integration Needs:
- Configure webhook URL
- Receive JSON POST on incidents
- Automate responses
- Integrate with your monitoring
Setup:
1. Account API Settings
2. Create Webhook Endpoint
3. Subscribe to Events
4. Test webhook
Part 9: Status Page History
How to View Past Incidents
Incident History:
On Status Page:
1. Look for "History" or "Incidents" tab
2. View past 30-90 days of incidents
3. Click on any incident for details
4. See timeline of updates
5. View root cause analysis
6. Review preventive measures
Details Include:
- Incident start time
- Root cause
- Impact assessment
- Resolution steps taken
- Lessons learned
- Preventive actions
View Analytics:
1. Go to "Performance" section
2. Select time period (7/30/90 days)
3. View uptime trends
4. Check response time graphs
5. See incident count
6. Review availability SLA
Part 10: SLA (Service Level Agreement)
Understanding SLAs
What is an SLA? A commitment by Neuro to maintain specific service levels
Standard SLA Targets:
Super Agent Service: 99.9% uptime
Research Service: 99.5% uptime
Content Generation: 99.8% uptime
Code Execution: 99.5% uptime
App Integration: 99.7% uptime
Image Generation: 98.0% uptime
Voice Service: 99.5% uptime
Database & Storage: 99.95% uptime
Enterprise Customers:
- Service credits applied automatically
- Escalated support response
- Root cause analysis provided
- Preventive measures implemented
Calculation Example:
- Target: 99.9% (≈44 min/month downtime)
- Actual: 99.5% (≈3.6 hours downtime)
- Difference: ~3.5 hours
- Credit: Percentage of monthly fee
Contact Support:
- Claims processed by support team
- SLA documentation required
- Credits applied next billing cycle
Part 11: Best Practices for Monitoring
Monitor System Health Regularly
DAILY:
- Check status page before critical tasks
- Verify services you'll use are operational
- Read any notices or warnings
WEEKLY:
- Review performance metrics
- Check incident history
- Adjust schedules if needed
MONTHLY:
- Review uptime statistics
- Check for patterns
- Plan around maintenance windows
Set Up Alerts
CRITICAL TASKS:
- Subscribe to email alerts
- Add SMS notifications
- Set up webhook monitoring
- Have backup plan ready
SCHEDULED TASKS:
- Avoid maintenance windows
- Build in buffer time
- Schedule important work off-peak
- Plan alternative if needed
INTEGRATIONS:
- Monitor integration status
- Test regularly
- Have manual workaround
- Alert on failures
Prepare for Outages
BUSINESS CONTINUITY:
- Have backup tools ready
- Document manual processes
- Keep offline copies of data
- Plan for extended outages
COMMUNICATION:
- Keep customer contact info
- Have outage message prepared
- Plan notification sequence
- Document impact
RECOVERY:
- Know what to verify when service returns
- Have data sync procedures
- Plan for data reconciliation
- Document lessons learned
Part 12: Getting Help
Support Options
Status Page Status:
- Real-time service status
- Incident information
- Estimated resolution times
- No login required
Support Portal:
- Login to your account
- Create support tickets
- Track issue resolution
- Access documentation
Email Support:
Phone Support (Enterprise):
- Direct phone line
- Immediate response
- Critical issues only
- SLA included
USE STATUS PAGE IF:
- Checking general service status
- Looking for incident information
- Seeing error messages
- Wondering if it's a widespread issue
USE EMAIL SUPPORT IF:
- Non-urgent question
- Account issue
- Feature question
- Documentation needed
USE CHAT SUPPORT IF:
- Need quicker response
- Have multiple questions
- Need guided help
- Premium member
USE PHONE SUPPORT IF:
- Business-critical issue
- Immediate help needed
- Enterprise customer
- Complex problem
Remember
- Status page is always available (even if service is down)
- Team is working on every incident
- You’re not alone if something’s wrong
- Support is ready to help
- System is constantly improving
Neuro AI Status Page & System Health Documentation
Monitor. Prepare. Succeed.
Real-time visibility into your AI assistant’s health and performance.
Last updated: January 2026