Zipy
  • Welcome to Zipy ai
  • Getting Started
    • Install Zipy
    • Installing with Google Tag Manager
    • Supported frameworks
    • Security Overview
    • Sensitive User Data
    • SOC2 Type II
  • Zipy For Mobile
    • React Native Setup
      • Install React Native
      • Input Masking
      • Session Replay
      • Screen Transition Capture
      • Gesture Capturing
      • Unhandled Exception Capture
      • Custom Logging
      • Fetch and XHR Network Calls
      • Profiling
      • Device Information Capture
      • Session URL Retrieval
      • Identify Users
      • Firebase Integration
    • Flutter Setup
      • Install Flutter
      • Session Replay
      • Input Masking & Custom Masking
      • Screen Transition Capture
      • Gesture Capturing
      • Unhandled Exception Capture
      • Custom Logging
      • Http Network Calls
      • Dio Network Calls
      • Profiling
      • Device Information Capture
      • Session URL Retrieval
      • Identify Users
      • Firebase Integration
      • Session Recording Control
      • Data Sanitization
  • iOS Setup
    • Install in an iOS app
    • Identify Users
    • Screen Tracking & Tagging
    • Custom Logging
    • Session URL Retrieval
    • Session Recording Control
    • Input Masking & Custom Masking
  • Chrome Extension
    • Zipy Plug and Play Support
  • Configure
    • Zipy Recording Control
    • Release Version
    • Identifying Users
    • Adding Custom Identifiers
    • Anonymize Users
    • Source Maps
    • Blocking PII data
    • Ignoring Errors/Noise
    • npm Update
    • Support Integration
    • Session Stitching (rootDomain)
  • Product Features
    • Custom Events
    • Session Replay
    • Errors
    • Analytics
    • Time Filters
    • Multiple Filters
    • Clicked Element Filters
    • Manage Teams
    • Stack Trace
    • Console Logs
    • Network Requests
    • Network Headers and Payload
    • Custom Logs
    • Live Users
    • Alerts
      • Slack Alerts
      • Email Alerts
      • Live Alerts
      • Custom Alerts
    • Auto Resolve Errors
    • Zipy Labels Plugin
    • iFrame Support
    • API Performance
    • Heatmaps
    • Page Performance
    • Seen/Unseen Sessions
    • Public Session URL
  • FAQs
    • Install Zipy
    • Session Replay Definition
    • Error Tracking
    • Error Classification
    • Environment Support
    • Impact on your App
    • Performance Impact
    • Mobile Support
    • Network Data Capture
    • API Performance Diagnostic Help
      • High DNS Time
      • High SSL Connection Time
      • High Connection Setup Time
      • Large API Response Size
      • High Response Time
      • Compression Not Enabled
      • Server side API Failures
      • Client side API Failures
      • Insecure Connections
  • Troubleshooting
    • Errors in npm
    • Network header missing in Zipy
    • Can't see user data in sessions
    • No recordings or errors visible
    • No network timing split available
  • Product Videos
    • Ask AI
    • Getting Started
    • Session Replay
    • Multiple Project Creation
    • Team Management
    • Alerting on Slack
    • Time Filters and Daily Alerts
    • Custom Identifiers
    • Ignore Errors
    • Identify Users
    • Dashboard
    • Resolve Errors
    • New Error Digest
    • Jira and Slack
    • Online/Offline Network Status
    • Zipy on Zipy
      • Zipy Product Roadmap
  • Whats new
    • Product Updates
  • Legal & Policy
    • Terms of Service
    • Privacy Policy
    • Fulfillment Policy
    • Cookie Policy
    • Acceptable Usage Policy
    • Zipy Sub Processor List
  • Integration
    • Azure DevOps
    • Factors
    • RB2B
    • Webflow
    • WordPress
    • Amplitude
    • Coralogix
    • DevRev
    • Drift
    • Errorception
    • Freshchat
    • Google Analytics
    • Heap
    • HelpScout
    • Honeybadger
    • Hubspot
    • Intercom
    • Mixpanel
    • New Relic
    • Pendo
    • Raygun
    • Rollbar
    • Segment
    • Sentry
    • Shopify
    • Sumo Logic
    • TrackJS
    • Zendesk
Powered by GitBook
On this page
  • Why am I seeing this diagnostic?
  • How do I fix this?
  1. FAQs
  2. API Performance Diagnostic Help

Server side API Failures

Why am I seeing this diagnostic?

When your webapp makes API calls, you expect to receive successful responses from the API servers. However, API failures can occur. If the failures happen on the API server when processing the request, they are indicated by HTTP 5xx status codes. These codes generally indicate server-side errors. Some common 5xx status codes include: 500 Internal Server Error, 502 Bad Gateway, 503 Service Unavailable, 504 Gateway Timeout etc.

When your APIs are failing with 5xx errors, it can have several implications for you as a webapp developer:

  1. Disrupted Functionality: API failures can disrupt the functionality of your webapp that relies on those APIs. It can result in incomplete or incorrect data, non-functional features, or even complete unavailability of specific services.

  2. Degraded User Experience: When API calls fail, your webapp may not be able to perform certain actions or retrieve necessary data, leading to a degraded user experience. Users may encounter errors, unexpected behavior, or inability to complete tasks.

  3. Performance Impact: Frequent API failures and increased server-side errors can impact the overall performance of your webapp. It may result in increased response times, decreased throughput, and increased server load due to retries or error handling logic.

How do I fix this?

To address API failures with 5xx errors, consider the following:

  1. Error Monitoring and Logging: Implement robust logging and error monitoring mechanisms to track API failures and diagnose their causes. This can help you identify patterns, troubleshoot issues, and work towards resolving them promptly.

  2. Retry Mechanisms: Implement retry logic in your webapp to automatically retry failed API requests. However, be mindful of retry strategies to avoid overwhelming the API servers or creating an endless retry loop.

  3. Error Handling and Graceful Degradation: Handle API failures gracefully in your webapp by displaying informative error messages to users and providing alternative functionalities or fallback options where possible.

  4. Communication with API Providers/Teams: Establish communication channels with the API providers or Backend Teams to report and inquire about the API failures. They might be able to provide insights, updates, or suggestions to resolve the issues.

PreviousCompression Not EnabledNextClient side API Failures

Last updated 2 years ago