Bvoip driftsforstyrrelser

1. 1. september 2026 kl. 11.23 UTCresolved

   August 31, 2026 1: 51PM EDT Identificeret - Vi er klar over en Microsoft udstationeret udfald for Exchange online. Du kan se, at dette bliver rapporteret flere steder. http: / / www.bleepingcomputer.com / news / microsoft / microsoft-exchange- online- outage- causes- email- failures- auth- issues / 1. Hvis du er e-mailer 1Stream, er det sandsynligt, at dine beskeder ikke når os for salg, support, osv. Vores systemer er online, men e-mail er sandsynligvis ikke at blive leveret. 2. Hvis du bruger M365 til udgående e-mail fra din 1Stream konto for ting som advarsler, voicemail- to- e-mail, osv. er det sandsynligt, at disse meddelelser ikke bliver sendt. 31 August, 2026 8: 45PM EDT Monitoring - Vi ser forsinket e-mail begynder at hælde ind fra ca middag østlige tid i dag, når Microsoft 365 / Exchange Online udfald startede. Vi vil fortsætte med at overvåge har alle Microsoft-tjenester er tilbage til 100%. September 1, 2026 7: 23AM Edt Opløst - Det ser ud til Microsoft 's udfald fra i går blev ryddet op omkring kl. 11 New York tid. Her er den bogførte tidslinje https: / / mashable.com / tech / microsoft- outlook- outage- aug- 31

Automatisk oversat fra den officielle hændelsesopdatering.

1. 23. august 2026 kl. 22.00 UTCresolved

   30 juli 2026 2: 43PM EDT Planlagt - Vores datacenter leverandør rådgivet os om følgende vedligeholdelse i vores Sydney datacenter region: Som en del af vores igangværende netværk infrastruktur opgraderinger, vi har planlagt en hardware udskiftning i en af vores kontakter i Sydney. Berørte servere vil opleve nedetid på op til 60 minutter under vedligeholdelsesvinduet. For at minimere virkningen på dine tjenester, vil arbejdet finde sted i løbet af natten. De angiver tidsvinduet er 8 timer, men de sigter mod 5-6 AM Sydney tid. August 23, 2026 2: 00PM EDT Aktiv - Planlagt netværksinfrastruktur opgradering i Sydney - Aug 24 - Vindue fra 23 August 2026 6: 00PM EDT Afsluttet - Planlagt netværksinfrastruktur opgradering i Sydney - Aug 24 - Window Ending

Automatisk oversat fra den officielle hændelsesopdatering.

1. 27. juli 2026 kl. 14.11 UTCresolved

   26 juli 2026 7: 31AM EDT Overvågning - Dette er et indlæg med tilbagevirkende kraft. Vores datacenter leverandør i Los Angeles fortalte os, at der var en delvis forbindelse afbrydelse i Los Angeles er siden blevet løst, Spørgsmålet startede kl 11: 34 og løst som 3: 04 Los Angeles tid. Den samlede varighed af udstedelsen var 3 timer og 40 minutter. Dette er, hvad der blev rapporteret til os: Hændelsen skyldtes en hardwarefejl i en af netværksenhederne, der betjener de berørte servere. Den defekte komponent blev erstattet, og en yderligere software justering var nødvendig under gendannelsesprocessen, før normal drift kunne genoprettes. 27 juli 2026 10: 11AM Edt Opløst - Lukning hændelse

Automatisk oversat fra den officielle hændelsesopdatering.

1. 14. juli 2026 kl. 13.29 UTCresolved

   8. juli 2026 11: 08AM EDT Identificeret - Vi har modtaget flere rapporter fra konti ved hjælp af kaldeplaner på siptrink.com / flowroute / nexvortex. Dette er et spørgsmål om bærestof, og vi er eskaleret til vores niveau 3 eskaleringsvej med bcmon. Vi er fundet, at specielt til siptrunk.com disse indstillinger ændringer giver nogle hjælp til at ændre gateways i brug fra gw1.siptrunk & gw2. siptrunk til gw4 og gw5 henholdsvis Deaktivering af trunk indstilling Mulighed "PBX leverer lyd" 8 juli 2026 1: 24 PM EDT Identificeret - Opdatering fra siptrunk.com Tak for denne information. Jeg har yderligere optrappet sagen til vores udviklings- og ingeniørhold, og de har meddelt, at de i øjeblikket er klar over interne problemer, som potentielt kan påvirke RTP 's lydtrafik og forhindre lydpakker i at passere korrekt. Vores hold undersøger aktivt problemet og undersøger, om de rapporterede symptomer stemmer overens med den adfærd, der i øjeblikket observeres internt. På nuværende tidspunkt synes dette at være det mest sandsynlige fokusområde baseret på de tilgængelige oplysninger. Vi vil fortsat overvåge situationen nøje og koordinere med de relevante hold. Så snart vi modtager yderligere resultater eller bekræftelse vedrørende den grundlæggende årsag og løsning, vil jeg give dig en opdatering straks. Tak for Deres tålmodighed og samarbejde, mens vi arbejder med denne undersøgelse. 8 juli 2026 2: 37PM EDT Monitoring - Seneste fra siptunk.com / bcmon Tak for din tålmodighed, mens vi arbejdede gennem dette intermitterende lydspørgsmål. Den grundlæggende årsag var særligt udfordrende at identificere, fordi de berørte opkald var traversing flere gateways, hvilket gør det vanskeligt at isolere en fælles faktor. Efter at have indsamlet yderligere opkaldseksempler fra andre kunder og eskaleret sagen til vores udviklingsteam, besluttede vi, at problemet opstod inden for vores netværk. En intern sløjfe var årsag lydtrafik til at forbruge et alt for stort antal havne, hvilket resulterede i lyd forstyrrelser bliver rapporteret. Vores udviklingsteam implementerede korrigerende ændringer kl 1: 30 EDT, og da disse opdateringer blev foretaget, har kunderne rapporteret mærkbare forbedringer i opkald lydkvalitet. På nuværende tidspunkt beder vi om, at du fortsætter med at overvåge og teste dine tjenester, og lad os vide, om du oplever yderligere spørgsmål, så vi kan bekræfte, at sagen er blevet fuldstændig løst. 9. juli 2026 9: 23AM Edt Opløst - Lukning hændelse 9. juli 2026 12: 28PM Edt Undersøgelse - Vi havde en relativt stille morgen, men vi har fået nogle nye rapporter om indgående opkald spørgsmål, der peger tilbage til BCM en igen. Vi har fanget nogle eksempler og sendt dem tilbage til deres hold til gennemgang. 9. juli 2026 1: 29PM EDT Monitoring - Opdatering fra bcmone / siptrunk.com vores Development Engineering team informeret mig om, at de har gennemført en yderligere intern ændring med det formål at lindre indgående og udgående lydproblemer, der har fundet sted. På dette tidspunkt, bedes du gentage og fortsætte med at overvåge dine opkald for at bekræfte, at lyd nu passerer korrekt i begge retninger, og at problemet er blevet løst. Hvis du fortsætter med at opleve problemer, bedes du give nye opkaldseksempler, og vi vil med glæde undersøge yderligere. 14. juli 2026 9: 29AM Edt Opløst - Ingen opdateringer emne præsenteret siden sidste uge. Lukning af hændelse

Automatisk oversat fra den officielle hændelsesopdatering.

1. 3. juli 2026 kl. 15.46 UTCresolved

   July 2, 2026 9:55AM EDT Identified - We received some reports of users not being able to sign in via the control portal SSO with User Not Found. We have identified and remediating this issue. July 2, 2026 10:57AM EDT Monitoring - All sign-in issue seem to be resolved at this time. Switching this incident to monitoring July 3, 2026 11:46AM EDT Resolved - Closing this incident

1. 30. juni 2026 kl. 15.34 UTCresolved

   June 24, 2026 7:33AM EDT Identified - We are aware and are in the middle of resolving an sign-in issue in our North America control portal region June 24, 2026 7:56AM EDT Monitoring - We have resolved the sign-in issue in North America via all control portal url's. Switching status of this incident to monitoring June 24, 2026 1:19PM EDT Monitoring - We are following up from an issue that started earlier today that was originally thought to be all North America accounts but is now narrowed down to just accounts in our Virginia data center. We are looking into a repeat occurrence of errors with the control portal functions specific to that location. We are in the process of re-routing those functions elsewhere to work around the current errors that are being reported. June 24, 2026 2:00PM EDT Monitoring - At this time all control portal functions in Virginia are operating normally. We are setting this back to monitoring June 30, 2026 11:34AM EDT Resolved - Closing incident

1. 30. maj 2026 kl. 18.55 UTCresolved

   May 29, 2026 8:26PM EDT Investigating - Our systems are reporting a cluster in our Los Angeles data center has stopped responding. We are investigating May 29, 2026 8:32PM EDT Investigating - We have confirmed we can not reach LACLOUD05. We have reached out to our data center vendor in Los Angeles to investigate May 29, 2026 8:34PM EDT Identified - Our data center vendor has confirmed a power related issue. They are working on restoring. May 29, 2026 8:59PM EDT Identified - It looks like the power issue has been corrected. We are bringing back the affected accounts online now. Will provide more updates shortly May 29, 2026 9:26PM EDT Monitoring - All affected accounts based out of our Los Angeles data center are fully operational. If you need any help, feel free to contact our support team. May 29, 2026 10:01PM EDT Investigating - LACLOUD05 is reporting as unreachable again. Contacting our vendor again May 29, 2026 10:29PM EDT Identified - This was a second power event in Los Angeles which mimics the original incident earlier. Power has been restored. We are bringing affected accounts online again. May 29, 2026 11:12PM EDT Monitoring - All systems in our Los Angeles data center are fully operational at this time. Monitoritng May 30, 2026 2:55PM EDT Resolved - All remains functional after last night’s issue in our Los Angeles data center. Closing incident

1. 30. maj 2026 kl. 18.54 UTCresolved

   May 28, 2026 10:44PM EDT Monitoring - We have been alerted and confirmed that our servers in Vancouver became unreachable and then reachable again. We had an earlier incident of the same type earlier today. We are already in touch with our data center vendor and will leave this as monitoring May 30, 2026 2:54PM EDT Resolved - All remains functional in our Vancouver data center from earlier in the week. Closing this incident

1. 30. maj 2026 kl. 18.54 UTCresolved

   May 28, 2026 10:40PM EDT Investigating - We have been alerted and confirm one of our server clusters in the Dallas data center is unreachable. We are investigating May 28, 2026 10:49PM EDT Investigating - We our in touch with our data center vendor in Dallas who is investigating locally May 28, 2026 11:08PM EDT Identified - Our Dallas data center vendor confirms that a failed device needs to be replaced. We are moving forward with equipment swap. May 29, 2026 2:41AM EDT Identified - Equipment replacement has been completed by our Dallas data center vendor. Affected accounts are starting to return back to normal. May 29, 2026 3:27AM EDT Monitoring - All systems in Dallas back to normal. Monitoring May 30, 2026 2:53PM EDT Resolved - All remains functional in our Vancouver Data center from an incident earlier in the week. Closing this incident May 30, 2026 2:54PM EDT Resolved - Apologies, meant to say Dallas here

1. 28. maj 2026 kl. 19.26 UTCresolved

   May 28, 2026 3:26PM EDT Resolved - This is a retroactive post. We had a brief network connectivity disruption in our Vancouver data center. According to our tools the issue started at 2:54pm (New York Time) and everything was online again at 3:09pm. We were in the process of communicating with our data center vendor who confirmed there was an issue and mid call confirmed the issue was already resolved.

1. 18. maj 2026 kl. 14.56 UTCresolved

   May 18, 2026 6:53AM EDT Investigating - We are investigating an issue affecting some customers based out of our Los Angeles Data center. Our systems indicate its specific to one cluster. May 18, 2026 7:39AM EDT Monitoring - All services in Los Angeles are back to normal. We are doing some checking with our data center vendor to review this specific cluster. Monitoring. May 18, 2026 10:56AM EDT Resolved - We have been monitoring our Los Angeles data center cluster for the last 4 hours and all is running as expected. We spoke to our Los Angeles data center vendor and they confirm that other work was being done and one of our underlying servers was accidently affected due to an oversight of a human being on their side. Now that we know this wasn't a technical malfunction, and all remains working, we are proceeding to close this incident

1. 4. maj 2026 kl. 19.12 UTCresolved

   May 4, 2026 3:04PM EDT Investigating - We are looking into a control portal issue specifically in North America. The other regions seem to be working as expected. Access to system management and single sign-on are affected. May 4, 2026 3:12PM EDT Resolved - Control portal back to 100% in North America. All systems are behaving properly for system management and single sign-on