Precios
Historial de estadoActualizaciones RSSAPI de estado

Desarrollado por Uptimus

    Historial de interrupciones de Callfire

    50 incidentes de Callfire registrados desde septiembre de 2014, con actualizaciones oficiales, componentes afectados, duración y detalles de resolución.

    Volver al estado actual

    Number provisioning delays.

    Comenzó 25 de febrero de 2025 a las 17:27 UTC · 6h 46m

    IssuesIncidente menor
    1. 25 de febrero de 2025 a las 17: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. 26 de febrero de 2025 a las 0:13 UTCresolved

      This incident has been resolved.

    Number Provisioning Issues

    Comenzó 23 de julio de 2024 a las 22:34 UTC · 15h 23m

    Pending
    1. 23 de julio de 2024 a las 22: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. 24 de julio de 2024 a las 13: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.

    Comenzó 25 de mayo de 2023 a las 16:06 UTC · 30d 4h

    OutageIncidente crítico
    Componentes afectados
    Call TrackingVoice BroadcastAPISMS Text MessagingIVRCloud Call Center
    1. 25 de mayo de 2023 a las 16:07 UTCidentified

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

    2. 25 de mayo de 2023 a las 16:33 UTCidentified

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

    3. 26 de mayo de 2023 a las 14: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. 26 de mayo de 2023 a las 15:08 UTCidentified

      We are currently operational, thank you for your patience.

    5. 29 de mayo de 2023 a las 17:08 UTCmonitoring

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

    6. 1 de junio de 2023 a las 17: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. 24 de junio de 2023 a las 20: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

    Comenzó 8 de febrero de 2016 a las 16:19 UTC · 8m

    IssuesIncidente menor
    1. 8 de febrero de 2016 a las 16: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. 8 de febrero de 2016 a las 16:27 UTCresolved

      This incident has been resolved.

    CallFire System Outage

    Comenzó 6 de junio de 2015 a las 5:11 UTC · 41m

    Pending
    1. 6 de junio de 2015 a las 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. 6 de junio de 2015 a las 5:52 UTCresolved

      This incident has been resolved.

    CallFire System Delays

    Comenzó 20 de mayo de 2015 a las 2:58 UTC · 14h 45m

    Pending
    1. 20 de mayo de 2015 a las 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. 20 de mayo de 2015 a las 16: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. 20 de mayo de 2015 a las 17:43 UTCresolved

      All messaging capability has been restored.

    CallFire System Outage

    Comenzó 15 de mayo de 2015 a las 18:49 UTC · 38m

    Pending
    1. 15 de mayo de 2015 a las 18: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. 15 de mayo de 2015 a las 19:28 UTCresolved

      This incident has been resolved.

    CallFire System Delays

    Comenzó 14 de mayo de 2015 a las 22:01 UTC · 1h 26m

    Pending
    1. 14 de mayo de 2015 a las 22:01 UTCidentified

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

    2. 14 de mayo de 2015 a las 23:27 UTCresolved

      This incident has been resolved.

    CallFire Maintenance

    Comenzó 26 de marzo de 2015 a las 21:13 UTC · 10m

    Pending
    1. 26 de marzo de 2015 a las 21: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. 26 de marzo de 2015 a las 21:24 UTCresolved

      This incident has been resolved.

    CallFire System Outage

    Comenzó 26 de marzo de 2015 a las 19:23 UTC · 1m

    Pending
    1. 26 de marzo de 2015 a las 19: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. 26 de marzo de 2015 a las 19:24 UTCresolved

      This incident has been resolved.

    Text Messaging

    Comenzó 16 de marzo de 2015 a las 23:47 UTC · 2h 42m

    Pending
    1. 16 de marzo de 2015 a las 23:47 UTCidentified

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

    2. 17 de marzo de 2015 a las 2:28 UTCresolved

      This incident has been resolved.

    Website Performance Degradation

    Comenzó 2 de marzo de 2015 a las 20:27 UTC · 30m

    Pending
    1. 2 de marzo de 2015 a las 20: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. 2 de marzo de 2015 a las 20:57 UTCresolved

      Website responsiveness has been resolved.

    CallFire Legacy System (CF2) System Delays

    Comenzó 23 de febrero de 2015 a las 23:46 UTC · 55m

    Pending
    1. 23 de febrero de 2015 a las 23: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. 24 de febrero de 2015 a las 0: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

    Comenzó 17 de febrero de 2015 a las 14:57 UTC · 5h 59m

    IssuesIncidente menor
    1. 17 de febrero de 2015 a las 14: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. 17 de febrero de 2015 a las 19:12 UTCmonitoring

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

    3. 17 de febrero de 2015 a las 20:56 UTCresolved

      This issue is deemed resolved.

    67076 Short Code Issue

    Comenzó 6 de febrero de 2015 a las 20:48 UTC · 12m

    Pending
    1. 6 de febrero de 2015 a las 20: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. 6 de febrero de 2015 a las 21:00 UTCresolved

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

    CallFire Maintenance

    Comenzó 13 de enero de 2015 a las 17:14 UTC · 17m

    IssuesIncidente menor
    1. 13 de enero de 2015 a las 17: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. 13 de enero de 2015 a las 17:24 UTCmonitoring

      Maintenance is complete, Engineering teams are running final checks.

    3. 13 de enero de 2015 a las 17:31 UTCresolved

      Smoke tests are complete.

    CallFire System Delays

    Comenzó 9 de enero de 2015 a las 15:24 UTC · 53m

    Pending
    1. 9 de enero de 2015 a las 15:24 UTCinvestigating

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

    2. 9 de enero de 2015 a las 15:50 UTCmonitoring

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

    3. 9 de enero de 2015 a las 16:17 UTCresolved

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

    CallFire System Delays

    Comenzó 7 de enero de 2015 a las 19:48 UTC · 20m

    Pending
    1. 7 de enero de 2015 a las 19:48 UTCidentified

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

    2. 7 de enero de 2015 a las 20:07 UTCresolved

      This incident has been resolved.

    Outbound calling stalled

    Comenzó 21 de noviembre de 2014 a las 20:15 UTC · 8m

    Pending
    1. 21 de noviembre de 2014 a las 20:15 UTCidentified

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

    2. 21 de noviembre de 2014 a las 20:22 UTCresolved

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

    Performance Degradation

    Comenzó 21 de noviembre de 2014 a las 16:48 UTC · 1h 1m

    Pending
    1. 21 de noviembre de 2014 a las 16: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. 21 de noviembre de 2014 a las 17:30 UTCinvestigating

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

    3. 21 de noviembre de 2014 a las 17: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.