Talk2m - Notice history

Experiencing minor outage

Europe

Partial outage

Germany - Partial outage

Italy - Partial outage

Rest of Europe - Partial outage

US

Partial outage

East US - Partial outage

West US - Partial outage

South America - Partial outage

Japan - Partial outage

India - Partial outage

China - Partial outage

Southeast Asia - Partial outage

Australia - Partial outage

South Africa - Partial outage

Notice history

Sep 2024

DataMailbox issue
  • Resolved
    Resolved

    Talk2m experienced a degradation of service between Sep 18, 2024 14:20 PM (UTC) and Sep 18, 2024 14:34 PM (UTC)

    Service was partially unreachable during 15 minutes. Issue has been identified and solved.

Service Disruption: SMS Alerts and 2FA Authentication not working (China)
  • Investigating
    Investigating

    We are currently experiencing an issue affecting our customers in China. At this time, Talk2m SMS alerts and two-factor authentication (2FA) codes are not being delivered. Our technical team is actively investigating the cause of this disruption and is working to resolve it as quickly as possible.

    We understand the importance of these services and apologize for any inconvenience this may cause. We will provide updates as soon as more information becomes available.

    Thank you for your patience and understanding.

VPN41 issue
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    Part of the devices were moved to VPN57. They will stay there until new servers (VPN65 and VPN77) are set online to welcome them (this should be on 2024-11-07).

  • Identified
    Update

    We will move part of the devices to a new server.

  • Identified
    Identified

    VPN41 is critically loaded. This is causing problems with establishing tunnels to it.

    We're working on a solution to this problem.

  • Investigating
    Investigating
    We are currently investigating this incident.

Aug 2024

M2Web migration
  • Completed
    August 06, 2024 at 11:00 AM
    Completed
    August 06, 2024 at 11:00 AM
    Maintenance has completed successfully
  • Update
    August 06, 2024 at 9:27 AM
    In progress
    August 06, 2024 at 9:27 AM

    All connections to LAN devices (HTTP/S, VNC, RDP) established prior to 7:30 AM (UTC) are currently linked to the previous servers. Kindly ensure to log out and log back in M2Web by 1 PM (UTC). After this time, all existing connections to the old servers will be terminated.

  • Update
    August 06, 2024 at 8:52 AM
    In progress
    August 06, 2024 at 8:52 AM

    New servers are up and running. Old domains will soon be stopped. If you receive 404 error, make sure you are using the correct domains.

  • In progress
    August 06, 2024 at 7:00 AM
    In progress
    August 06, 2024 at 7:00 AM
    Maintenance is now in progress
  • Update
    August 06, 2024 at 7:00 AM
    Planned
    August 06, 2024 at 7:00 AM

    On Tuesday 2024-08-06, we will modernize all M2web servers. This action will trigger some changes.

    IP addresses and domain names of the regional M2web servers will be replaced by new ones. If you whitelist the IP addresses, or use regional servers (xx.m2web.talk2m.com) directly for Web browsing or through the M2web API (instead of using the correct server from "m2webServer" field - See "getewons" method in M2web API ref guide), you are required to take action.

    Here is the list of the URL changes:

    • au.m2web.talk2m.com: Replaced by au-1.m2web.talk2m.com

    • br.m2web.talk2m.com: Replaced by br-1.m2web.talk2m.com

    • eu1.m2web.talk2m.com: Replaced by m2web.talk2m.com

    • eu2.m2web.talk2m.com: Replaced by m2web.talk2m.com

    • in.m2web.talk2m.com: Replaced by in-1.m2web.talk2m.com

    • jp2.m2web.talk2m.com: Replaced by jp-1.m2web.talk2m.com

    • sg.m2web.talk2m.com: Replaced by sg-1.m2web.talk2m.com

    • uk1.m2web.talk2m.com: Replaced by m2web.talk2m.com

    • us4.m2web.talk2m.com: Replaced by us-e-1.m2web.talk2m.com

    • us5.m2web.talk2m.com: Replaced by us-c-1.m2web.talk2m.com

    • us6.m2web.talk2m.com: Replaced by us-e-1.m2web.talk2m.com

    • us7.m2web.talk2m.com: Replaced by us-w-1.m2web.talk2m.com

    • za2.m2web.talk2m.com: Replaced by za-1.m2web.talk2m.com

     

    The main M2web https://m2web.talk2m.com remains unchanged.

    If you whitelisted M2web servers from an IP level, you need to whitelist these new IP addresses:

    • 139.99.217.177

    • 18.230.252.76

    • 54.36.113.88

    • 79.137.11.244

    • 13.232.103.186

    • 13.114.27.70

    • 141.95.105.122

    • 52.74.70.80

    • 18.88.29.177

    • 3.18.254.81

    • 54.215.4.200

    • 13.245.130.51

    We don't expect any downtime during the maintenance. The switch will be performed automatically at 7AM (UTC).  The old domains will be deactivated at 9AM (UTC).  

  • Planned
    August 02, 2024 at 6:58 AM
    Planned
    August 02, 2024 at 6:58 AM

    Migration is confirmed to happen next Tuesday (2024-08-06).

    More detailed information about firewall requirements is available on this page: https://help.ewon.biz/ecatcher/help/en/talk2m-onsite-firewall-requirements.html

Jul 2024

VPN 48 issue
  • Resolved
    Resolved

    Talk2m experienced a degradation of service for vpn48 (roubaix) between 30 july 21:00 GMT and 31 July 03:30 GMT

    Because of degraded network performance on vpn48 server located in Europe, impacted Ewon devices were temporarily been routed to another server, between 31 july 00:00 GMT

    and 31 july 12:30 GMT.


    Affected service were ecatcher and m2web for devices connected to that server.

VPN40 (Australia) connection issue
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    VPN40 located in Sydney (Australia) may be unreachable from some locations in the world due to an Internet backbone issue (outside of our infrastructure).

    From the moment, devices have not been moved. Users located in Australia should be able to reach their devices.

    We'll keep you informed as soon as we have more information coming from our cloud providers.

    In case of you are unable to reach your device(s), please contact our Technical Support and provide details about your user and device locations.

VPN58 (India) is unavailable
  • Resolved
    Resolved

    This incident has been resolved. Devices were moved back to VPN58

  • Investigating
    Update

    Devices were moved to VPN34 (Singapore)

  • Investigating
    Investigating
    We are currently investigating this incident.
Maintenance Operation Planned on VPN16 (India)
Scheduled for July 02, 2024 at 7:00 AM – 9:00 AM about 2 hours
  • Update
    July 02, 2024 at 8:00 AM
    Completed
    July 02, 2024 at 8:00 AM
    Maintenance has completed successfully.
  • Completed
    July 02, 2024 at 7:57 AM
    Completed
    July 02, 2024 at 7:57 AM
    Maintenance has completed successfully
  • In progress
    July 02, 2024 at 7:00 AM
    In progress
    July 02, 2024 at 7:00 AM
    Maintenance is now in progress
  • Planned
    July 02, 2024 at 6:00 AM
    Planned
    July 02, 2024 at 6:00 AM

    On Tuesday, 2 July 2024, between 09:00 AM CEST (12:30 PM IST) and 11:00 AM CEST (14:30 PM IST), the VPN16 Server (device.vpn16.talk2m.com) located in India will be under maintenance. All Ewon devices connected to this server will be switched to a new VPN server (device.vpn58.talk2m.com) with a new public IP address (15.207.15.202). The Ewon devices will be briefly unavailable during this operation.

    Since the public IP address of the new VPN server will be different, your on-site firewall rules might need to be adjusted to whitelist this new IP address 15.207.15.202 / TCP443 / UDP1194. Failure to adjust your firewall rules before the maintenance date could lead to the disconnection of your devices.

    To take full advantage of the global Talk2m infrastructure, please review the best practices related to ports and addresses used by Talk2m, as explained on our Talk2m Onsite Firewall Requirements page.

    If you experience any issues after this maintenance, please do not hesitate to contact HMS Support.

Main m2web experiences degredation of its performances
  • Resolved
    Resolved

    Incident has been resolved. Everything should be back to normal

  • Investigating
    Investigating

    It may take some time to load the device list, VNC and RDP access seems to be malfunctioning.

    We are currently investigating this incident.

Jul 2024 to Sep 2024

Next