LinkedIn API incident

LinkedIn AccessToken and Authorization API Returning 429 Error

Notice Resolved View vendor source →

LinkedIn API experienced a notice incident on January 13, 2025, lasting 3h 38m. The incident has been resolved; the full update timeline is below.

Started
Jan 13, 2025, 04:22 PM UTC
Resolved
Jan 13, 2025, 08:01 PM UTC
Duration
3h 38m
Detected by Pingoru
Jan 13, 2025, 04:22 PM UTC

Update timeline

  1. investigating Jan 13, 2025, 04:22 PM UTC

    We are currently experiencing an issue across the platform that may cause some API requests to /v2/accessToken and /v2/authorization are returning a 429 error code. We are investigating the issue and working on a resolution.

  2. identified Jan 13, 2025, 06:37 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Jan 13, 2025, 06:42 PM UTC

    We are continuing to work on a fix for this issue.

  4. resolved Jan 13, 2025, 08:01 PM UTC

    We’re pleased to report that the issue affecting the platform, where some API requests to /v2/accessToken and /v2/authorization were returning a 429 error code, has now been resolved. Our team has implemented a fix, and all systems are back to normal operation. We sincerely appreciate your patience while we worked to resolve this matter. If you continue to encounter any issues, please contact our support team for assistance.