Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Vinsolutions 장애 기록

    20 Vinsolutions incidents · 2018년 7월 — official updates, affected components, duration and resolution details.

    현재 상태로 돌아가기

    Intermittent DNS Issues may affect API Requests

    시작 2021년 5월 6일 오후 6:42 UTC · 4h 45m

    Issues경미한 인시던트
    영향을 받은 구성 요소
    API Gateway
    1. 2021년 5월 6일 오후 6:42 UTCinvestigating

      We are monitoring, and taking proactive measures where possible, in response to intermittent DNS provider issues which may be impacting our integrator community.

    2. 2021년 5월 6일 오후 6:42 UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. 2021년 5월 6일 오후 11:27 UTCresolved

      Service is restored.   From 1:40 P.M. to 4:15 P.M. EDT, Multiple CAI services and product lines experienced DNS related failures.

    API Gateway Degradation

    시작 2021년 3월 11일 오전 12:28 UTC · 30m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    API Gateway
    1. 2021년 3월 11일 오전 12:28 UTCidentified

      Mashery's service is currently degraded, which may affect Cox Automotive / Connect CRM API requests. You can obtain direct updates from Tibco here: https://status.cloud.tibco.com/incidents/bjzqyq4rvdmf.

    2. 2021년 3월 11일 오전 12:58 UTCresolved

      Update from Tibco/Mashery (https://status.cloud.tibco.com/incidents/bjzqyq4rvdmf) "Based on the available information at this time, we believe that the degradation has been addressed and we are seeing recovery. All Mashery service components are in good health. Mashery team is currently monitoring the situation. We are committed to providing you follow-up updates through Status page as soon as we have more information." Based on the above information, as well as verification that API requests are being fulfilled properly, we are closing this incident.

    Call Details API: long processing time and timeouts (HTTP 504)

    시작 2020년 12월 2일 오후 8:13 UTC · 9h 46m

    Issues경미한 인시던트
    영향을 받은 구성 요소
    Call Details API
    1. 2020년 12월 2일 오후 8:13 UTCinvestigating

      We are currently investigating this issue.

    2. 2020년 12월 2일 오후 9:22 UTCidentified

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

    3. 2020년 12월 2일 오후 10:40 UTCidentified

      We have scheduled a maintenance window for this evening to work on the performance issues with the Call Details API. Until then, the system will be operational, but in a degraded state.

    4. 2020년 12월 3일 오전 5:59 UTCresolved

      Maintenance and verification is complete.

    Call Details API: Degraded Performance/Longer Response Times

    시작 2020년 11월 30일 오후 10:11 UTC · 2h 32m

    Issues경미한 인시던트
    영향을 받은 구성 요소
    Call Details API
    1. 2020년 11월 30일 오후 11:22 UTCinvestigating

      Our Call Details API response times have degraded and we are investigating the matter. The issue results in excessive HTTP 504 (Gateway Timeout) responses. We are investigating.

    2. 2020년 12월 1일 오전 12:43 UTCresolved

      The Call Details API is now responding as expected.

    Call Details API

    시작 2020년 11월 25일 오후 7:03 UTC · 44m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    API GatewayCall Details API
    1. 2020년 11월 25일 오후 7:03 UTCmonitoring

      The Call Details API is being affected by an incident with our network infrastructure provider beginning at approx. 5pm UTC. Multiple teams have been engaged and are working on the issue. Errors have begun to clear but we continue to monitor the situation.

    2. 2020년 11월 25일 오후 7:46 UTCmonitoring

      We are continuing to monitor for any further issues.

    3. 2020년 11월 25일 오후 7:46 UTCresolved

      This incident has been resolved.

    Vehicle Inventory: errors with some queries

    시작 2020년 4월 23일 오후 4:15 UTC · 1h 24m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    Vehicles API
    1. 2020년 4월 23일 오후 4:15 UTCinvestigating

      We are investigating reports of errors in response to some vehicle inventory requests using the Digital Showroom API.

    2. 2020년 4월 23일 오후 4:51 UTCidentified

      The issue has been identified and a fix will be applied momentarily.

    3. 2020년 4월 23일 오후 5:39 UTCresolved

      The incident affecting Vehicle Inventory queries has been resolved.

    Intermittent errors

    시작 2020년 2월 24일 오후 3:55 UTC · 5h 19m

    Outage중대한 인시던트
    영향을 받은 구성 요소
    Leads APIContacts API
    1. 2020년 2월 24일 오후 3:55 UTCinvestigating

      We are currently investigating reports of intermittent HTTP 500 / 504 responses affecting primarily the Contact endpoints. Multiple teams are engaged as this is a system-wide issue affecting the CRM.

    2. 2020년 2월 24일 오후 4:01 UTCinvestigating

      We are also investigating timeouts associated with requests to the Lead endpoints.

    3. 2020년 2월 24일 오후 5:20 UTCinvestigating

      We have placed the Contact API in maintenance mode while teams troubleshoot it. Requests to this endpoint will be responded to with HTTP 503 - Service Unavailable, with an additional header "Scheduled Maintenance."

    4. 2020년 2월 24일 오후 6:02 UTCidentified

      CRM performance has improved significantly for clients; however, we will leave the Contact endpoint in maintenance mode while engineering and I/T bring online other processes which were disabled during troubleshooting. We will remove maintenance mode once we receive the all clear that supporting processes are again online.

    5. 2020년 2월 24일 오후 7:50 UTCmonitoring

      After confirming CRM stability, we are now taking the Contact API out of maintenance mode. We continue to monitor the CRM's performance for slowness and will take corrective actions as necessary.

    6. 2020년 2월 24일 오후 9:14 UTCresolved

      CRM and API performance have returned to normal levels.

    Leads Impairment

    시작 2020년 2월 11일 오후 4:07 UTC · 45m

    Pending
    영향을 받은 구성 요소
    Leads API
    1. 2020년 2월 11일 오후 4:07 UTCinvestigating

      We are currently investigating an issue affecting our Leads APIs.

    2. 2020년 2월 11일 오후 4:52 UTCresolved

      The issue has been resolved.

    HTTP 401 Responses to Organizations and Users Requests

    시작 2019년 12월 19일 오후 3:24 UTC · 21m

    Outage심각한 인시던트
    영향을 받은 구성 요소
    Organizations APIUsers API
    1. 2019년 12월 19일 오후 3:24 UTCidentified

      We identified the issue causing HTTP 401 responses when requests are made to our Organizations and Users endpoints.

    2. 2019년 12월 19일 오후 3:45 UTCresolved

      The incident has been resolved and we have confirmed that requests for Organizations and Users are processing as expected.

    API request timeouts

    시작 2019년 11월 20일 오후 6:13 UTC · 3h 11m

    Pending
    영향을 받은 구성 요소
    Leads APIVehicles APIOrganizations APIContacts APIUsers APICall Details API
    1. 2019년 11월 20일 오후 6:13 UTCinvestigating

      We are currently investigating an issue affecting our API infrastructure which results in API request timeouts.

    2. 2019년 11월 20일 오후 8:36 UTCmonitoring

      A fix has been implemented and we are monitoring the results. We are seeing fewer HTTP 5xx errors.

    3. 2019년 11월 20일 오후 9:25 UTCresolved

      This incident has been resolved.

    Identity Services impairment

    시작 2019년 8월 26일 오후 3:45 UTC · 10h 38m

    Pending
    영향을 받은 구성 요소
    Authentication
    1. 2019년 8월 26일 오후 4:39 UTCinvestigating

      We are currently investigating an issue with our Identity services which impacts the CRM and APIs. The issue began at approximately 10:45am CDT.

    2. 2019년 8월 26일 오후 4:44 UTCmonitoring

      A fix has been implemented and we will monitor throughout the day.

    3. 2019년 8월 27일 오전 2:23 UTCresolved

      This incident has been resolved.

    Identity Server / Authentication Issue

    시작 2019년 8월 23일 오후 7:35 UTC · 3h 12m

    Pending
    영향을 받은 구성 요소
    Authentication
    1. 2019년 8월 23일 오후 7:35 UTCinvestigating

      We are currently investigating an issue affecting authentication.

    2. 2019년 8월 23일 오후 7:49 UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. 2019년 8월 23일 오후 10:47 UTCresolved

      This incident has been resolved.

    Call Details API: Additional HTTP 500 responses

    시작 2019년 7월 31일 오후 5:00 UTC · 55m

    Outage심각한 인시던트
    영향을 받은 구성 요소
    Call Details API
    1. 2019년 7월 31일 오후 5:00 UTCinvestigating

      We are currently investigating an issue which affects the Call Details API.

    2. 2019년 7월 31일 오후 7:27 UTCresolved

      The Call Details API incident has been resolved.

    Call Details API: HTTP 502 and 504 Errors

    시작 2019년 7월 31일 오후 2:39 UTC · 1h 37m

    Outage심각한 인시던트
    영향을 받은 구성 요소
    Call Details API
    1. 2019년 7월 31일 오후 2:39 UTCinvestigating

      Call details API is experiencing an issue. No other APIs are affected.

    2. 2019년 7월 31일 오후 3:50 UTCresolved

      The Call Details API is operational and requests are successfully processing.

    Leads: Intermittent HTTP 500 responses

    시작 2019년 1월 26일 오후 9:21 UTC · 21h 22m

    Issues경미한 인시던트
    영향을 받은 구성 요소
    Leads API
    1. 2019년 1월 26일 오후 9:21 UTCidentified

      We are working on a fix to an issue affecting the creation, and updating, of leads via the API.

    2. 2019년 1월 26일 오후 9:40 UTCinvestigating

      We are gathering more information.

    3. 2019년 1월 27일 오전 5:07 UTCinvestigating

      We are working with our API Gateway provider to understand why Leads requests are returning HTTP 500 responses intermittently.

    4. 2019년 1월 27일 오후 6:43 UTCresolved

      This incident has been resolved.

    Associate Vehicle of Interest: "Could not find auto associated with this autoId"

    시작 2018년 10월 23일 오후 8:05 UTC · 1d 1h

    Pending
    1. 2018년 10월 23일 오후 8:05 UTCidentified

      The Leads API is not able to associate a vehicle of interest in some cases. The root cause has been identified and a fix is being developed.

    2. 2018년 10월 24일 오전 2:14 UTCidentified

      The fix is planned to be deployed to production tomorrow morning. We will send an update after successful deployment.

    3. 2018년 10월 24일 오후 4:46 UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. 2018년 10월 24일 오후 9:51 UTCresolved

      This incident has been resolved.

    HTTP 500 Responses: Lead API Timeouts

    시작 2018년 9월 26일 오후 6:09 UTC · 5d 1h

    Pending
    1. 2018년 9월 26일 오후 6:09 UTCidentified

      We are currently investigating timeouts which result in HTTP 500 responses to Leads API requests.

    2. 2018년 9월 26일 오후 9:06 UTCidentified

      A fix is being developed for issues affecting the Lead PUT method.

    3. 2018년 9월 27일 오후 7:06 UTCidentified

      The fix for the PUT Lead errors has passed QA and will roll to production soon.

    4. 2018년 9월 27일 오후 7:52 UTCmonitoring

      The fix has been deployed and verified in Production. When notes are included with POST / PUT Customer and Lead requests, HTTP 500 responses do not appear and the operation completes successfully.

    5. 2018년 10월 1일 오후 8:08 UTCresolved

      This incident has been resolved.

    HTTP 500 Responses to PUT Lead Requests

    시작 2018년 8월 22일 오후 2:46 UTC · 11d 22h

    Issues경미한 인시던트
    영향을 받은 구성 요소
    Leads API
    1. 2018년 8월 22일 오후 2:46 UTCinvestigating

      We are currently investigating reports of unexpected HTTP 500 responses to Lead PUT requests. The same request body, submitted subsequently, results in HTTP 200 (success).

    2. 2018년 8월 24일 오후 5:25 UTCidentified

      We've seen a reduction in the percentage of HTTP 500 responses; but, we are also developing a fix to further reduce the frequency of these responses to the PUT Leads requests.

    3. 2018년 8월 27일 오후 3:59 UTCmonitoring

      We've implemented changes to reduce the frequency of the HTTP 500 errors. We will monitor for 1 week to gather data about the success of our changes before "resolving" this incident.

    4. 2018년 9월 3일 오후 1:21 UTCresolved

      This incident has been resolved based on feedback from our Partners and a measurable reduction in HTTP 500 responses.

    HTTP 500 responses on Leads POST

    시작 2018년 7월 31일 오후 5:21 UTC · 4h 9m

    Issues경미한 인시던트
    영향을 받은 구성 요소
    Leads API
    1. 2018년 7월 31일 오후 5:21 UTCinvestigating

      We are currently investigating issues reported with the Leads API.

    2. 2018년 7월 31일 오후 9:29 UTCresolved

      After researching the issue, we found that, when an invalid AutoID is used in the body of the associateVehicleOfInterest operation, the server responds with HTTP 500. To prevent the HTTP 500 response, please be sure to use valid AutoIDs provided by the getVehicleInventory operation. In the future, we will provide better messaging to handle this scenario.

    Authorization impairment

    시작 2018년 7월 19일 오전 12:23 UTC · 16h 50m

    Outage중대한 인시던트
    1. 2018년 7월 19일 오후 5:57 UTCresolved

      Dealer hierarchy services were impaired between 16:47 and 17:13 UTC, causing API requests for Dealership data to fail with HTTP 500 responses.