Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Callfire 장애 기록

    50 Callfire incidents · 2014년 9월 — official updates, affected components, duration and resolution details.

    현재 상태로 돌아가기

    Number provisioning delays.

    시작 2025년 2월 25일 오후 5:27 UTC · 6h 46m

    Issues경미한 인시던트
    1. 2025년 2월 25일 오후 5:27 UTCinvestigating

      A key industry partner is experiencing delays with the provisioning of new numbers. New customers completing carrier registration and existing customers purchasing a new number for texting may be affected. This issue is currently affecting many in our industry. If you have recently submitted your carrier registration, we recommend subscribing to our status page so that you’ll receive the all latest updates as we learn more from our partner - - they are expecting that they will have a resolution to this issue today. We deeply apologize for the inconvenience.

    2. 2025년 2월 26일 오전 12:13 UTCresolved

      This incident has been resolved.

    Number Provisioning Issues

    시작 2024년 7월 23일 오후 10:34 UTC · 15h 23m

    Pending
    1. 2024년 7월 23일 오후 10:34 UTCidentified

      An outage with a core industry entity is causing delays with the provisioning of local numbers for texting. Voice services are not affected. We recommend that you refrain from switching SMS service to a new number at this time, if you have an existing number that is already live. We will share more information as soon as we've received an update from our industry partners.

    2. 2024년 7월 24일 오후 1:57 UTCresolved

      The provisioning outage has been resolved. Thank you for patience.

    We are experiencing platform disruptions that are affecting application services, API calls, and logins. Systems will be intermittently operational. Thank you for your patience while we continue to investigate and work towards a fix.

    시작 2023년 5월 25일 오후 4:06 UTC · 30d 4h

    Outage심각한 인시던트
    영향을 받은 구성 요소
    Call TrackingVoice BroadcastAPISMS Text MessagingIVRCloud Call Center
    1. 2023년 5월 25일 오후 4:07 UTCidentified

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

    2. 2023년 5월 25일 오후 4:33 UTCidentified

      Our systems are currently up and running. Thank you for your patience

    3. 2023년 5월 26일 오후 2:23 UTCidentified

      We are experiencing platform disruptions that are affecting application services, API calls, and logins. Systems will be intermittently operational. Thank you for your patience while we continue to investigate and work towards a fix.

    4. 2023년 5월 26일 오후 3:08 UTCidentified

      We are currently operational, thank you for your patience.

    5. 2023년 5월 29일 오후 5:08 UTCmonitoring

      Update - The system is currently operational. We are continuing to monitor for intermittent platform disruptions.

    6. 2023년 6월 1일 오후 5:00 UTCmonitoring

      Our emergency response team continues to monitor our systems 24/7. Our Engineers continue to work on several fixes and optimizations that are cumulatively working well. The platform has not had any downtime since Friday morning May 26th. We will continue to update once resolved.

    7. 2023년 6월 24일 오후 8:23 UTCresolved

      All systems are operational since 5/26, with the exception of a brief and unrelated issue on 6/23. Note that we will be deprecating this statuspage. Moving forward, please subscribe to our new statuspage https://status.eztexting.com/ where we will share updates for both the Callfire and EZ Texting brands.

    Performance Degradation

    시작 2016년 2월 8일 오후 4:19 UTC · 8m

    Issues경미한 인시던트
    1. 2016년 2월 8일 오후 4:19 UTCinvestigating

      CallFire systems are currently performing more slowly than usual. Please be advised that your campaigns continued to be processed. We expect performance to improve shortly.

    2. 2016년 2월 8일 오후 4:27 UTCresolved

      This incident has been resolved.

    CallFire System Outage

    시작 2015년 6월 6일 오전 5:11 UTC · 41m

    Pending
    1. 2015년 6월 6일 오전 5:11 UTCidentified

      We are currently experiencing a system outage. Our engineers are aware of the situation and are working to resolve it. We apologize for the inconvenience.

    2. 2015년 6월 6일 오전 5:52 UTCresolved

      This incident has been resolved.

    CallFire System Delays

    시작 2015년 5월 20일 오전 2:58 UTC · 14h 45m

    Pending
    1. 2015년 5월 20일 오전 2:58 UTCmonitoring

      Our downstream carriers are experiencing delays on sending and receiving on our 67076 Short Code. We are working with them to restore service.

    2. 2015년 5월 20일 오후 4:23 UTCmonitoring

      Our upstream providers are experiencing transmission issues. SMS delivery to some mobile provider networks may be delayed or in some cases may fail. We are working diligently with all parties to ensure quick resolution of this issue and sincerely apologize for any inconvenience.

    3. 2015년 5월 20일 오후 5:43 UTCresolved

      All messaging capability has been restored.

    CallFire System Outage

    시작 2015년 5월 15일 오후 6:49 UTC · 38m

    Pending
    1. 2015년 5월 15일 오후 6:49 UTCidentified

      We are currently experiencing a system outage with several products. Our engineers are aware of the situation and are working to resolve it. We apologize for the inconvenience.

    2. 2015년 5월 15일 오후 7:28 UTCresolved

      This incident has been resolved.

    CallFire System Delays

    시작 2015년 5월 14일 오후 10:01 UTC · 1h 26m

    Pending
    1. 2015년 5월 14일 오후 10:01 UTCidentified

      The CallFire platform is currently experiencing system delays. We are working to resolve the issue as quickly as possible.

    2. 2015년 5월 14일 오후 11:27 UTCresolved

      This incident has been resolved.

    CallFire Maintenance

    시작 2015년 3월 26일 오후 9:13 UTC · 10m

    Pending
    1. 2015년 3월 26일 오후 9:13 UTCidentified

      The CallFire system is undergoing maintenance. This currently affects all reporting on our legacy platform. We are working to restore service as soon as possible.

    2. 2015년 3월 26일 오후 9:24 UTCresolved

      This incident has been resolved.

    CallFire System Outage

    시작 2015년 3월 26일 오후 7:23 UTC · 1m

    Pending
    1. 2015년 3월 26일 오후 7:23 UTCidentified

      We are currently experiencing a system outage. Our engineers are aware of the situation and are working to resolve it. We apologize for the inconvenience.

    2. 2015년 3월 26일 오후 7:24 UTCresolved

      This incident has been resolved.

    Text Messaging

    시작 2015년 3월 16일 오후 11:47 UTC · 2h 42m

    Pending
    1. 2015년 3월 16일 오후 11:47 UTCidentified

      CallFire has identified intermittent failures when sending SMS messages through certain carriers.  Our carriers are working to resolve the issue.

    2. 2015년 3월 17일 오전 2:28 UTCresolved

      This incident has been resolved.

    Website Performance Degradation

    시작 2015년 3월 2일 오후 8:27 UTC · 30m

    Pending
    1. 2015년 3월 2일 오후 8:27 UTCidentified

      The CallFire website is currently performing slower than usual. Please be advised that your campaigns continue to be processed. We expect performance to improve shortly.

    2. 2015년 3월 2일 오후 8:57 UTCresolved

      Website responsiveness has been resolved.

    CallFire Legacy System (CF2) System Delays

    시작 2015년 2월 23일 오후 11:46 UTC · 55m

    Pending
    1. 2015년 2월 23일 오후 11:46 UTCidentified

      The CallFire platform is currently experiencing system delays. We are working to resolve the issue as quickly as possible. If you can, please consider moving to our new Tesla platform.

    2. 2015년 2월 24일 오전 12:42 UTCresolved

      The capacity issue has been solved. If you have any questions about moving to our new platform, please contact one of our friendly Client Success Managers.

    CallFire System Delays

    시작 2015년 2월 17일 오후 2:57 UTC · 5h 59m

    Issues경미한 인시던트
    1. 2015년 2월 17일 오후 2:57 UTCidentified

      The CallFire platform is currently experiencing system delays. Voice calls are being reported slowly which can result in campaigns going out slower than usual. We are working to resolve the issue as quickly as possible.

    2. 2015년 2월 17일 오후 7:12 UTCmonitoring

      The issue has been deemed resolved as of 8:00 AM PST. The CallFire engineering team will continue to monitor.

    3. 2015년 2월 17일 오후 8:56 UTCresolved

      This issue is deemed resolved.

    67076 Short Code Issue

    시작 2015년 2월 6일 오후 8:48 UTC · 12m

    Pending
    1. 2015년 2월 6일 오후 8:48 UTCidentified

      Our provider is currently having issues delivering messages over the 67076 short code. We are working with them to resolve the issue as quickly as possible.

    2. 2015년 2월 6일 오후 9:00 UTCresolved

      The provider has resolved the issue. Text messages from the 67076 short code are now working.

    CallFire Maintenance

    시작 2015년 1월 13일 오후 5:14 UTC · 17m

    Issues경미한 인시던트
    1. 2015년 1월 13일 오후 5:14 UTCidentified

      The CallFire system is undergoing maintenance. This currently affects all products on our platform: Voice Broadcast, Cloud Call Center, Call Tracking, and SMS Text Messaging. We are working to restore service as soon as possible.

    2. 2015년 1월 13일 오후 5:24 UTCmonitoring

      Maintenance is complete, Engineering teams are running final checks.

    3. 2015년 1월 13일 오후 5:31 UTCresolved

      Smoke tests are complete.

    CallFire System Delays

    시작 2015년 1월 9일 오후 3:24 UTC · 53m

    Pending
    1. 2015년 1월 9일 오후 3:24 UTCinvestigating

      The CallFire platform is currently experiencing system delays. We are working to resolve the issue as quickly as possible.

    2. 2015년 1월 9일 오후 3:50 UTCmonitoring

      Contact list validations are working smoothly. The engineering team is monitoring the issue before marking it as being resolved.

    3. 2015년 1월 9일 오후 4:17 UTCresolved

      After monitoring contact list validation, the engineering team has determined that the issue has been resolved.

    CallFire System Delays

    시작 2015년 1월 7일 오후 7:48 UTC · 20m

    Pending
    1. 2015년 1월 7일 오후 7:48 UTCidentified

      The CallFire platform is currently experiencing system delays. We are working to resolve the issue as quickly as possible.

    2. 2015년 1월 7일 오후 8:07 UTCresolved

      This incident has been resolved.

    Outbound calling stalled

    시작 2014년 11월 21일 오후 8:15 UTC · 8m

    Pending
    1. 2014년 11월 21일 오후 8:15 UTCidentified

      This includes all outbound: IVR, VB, and agent callbacks.

    2. 2014년 11월 21일 오후 8:22 UTCresolved

      We are now working to query the timeouts and resend them.

    Performance Degradation

    시작 2014년 11월 21일 오후 4:48 UTC · 1h 1m

    Pending
    1. 2014년 11월 21일 오후 4:48 UTCinvestigating

      We are investigating several issues now, including list validation and inbound SMS to long codes. Nothing is confirmed now. We will update.

    2. 2014년 11월 21일 오후 5:30 UTCinvestigating

      Long code SMS issue repaired. Turning attention to list validation.

    3. 2014년 11월 21일 오후 5:48 UTCresolved

      List validation is not universal. Two lists were found to have problems, and they are being addressed, but in general, the validation is working normally. Except for the power problems, the system is operational.