200 X-Frame-Options: SAMEORIGIN Content-Security-Policy: frame-ancestors 'self'; X-UA-Compatible: IE=Edge X-XSS-Protection: 1; mode=block X-Content-Type-Options: nosniff X-Telligent-Evolution: 12.x Pragma: no-cache Connection: close Accept-Ranges: bytes Cache-Control: no-store, no-cache, max-age=0 Date: Tue, 23 Sep 2025 22:26:39 GMT ETag: "0x8DDF5C624966A39" Set-Cookie: .te.csrf=h-Y77uEXjYsu7rL9a8KBamsulls4wnQM0OwivuzlLDk; path=/; secure; SameSite=Lax Set-Cookie: .te.auth=_WOGU88fHNWGqvzIBbeTtY2LWRoVyTMjZ0iZqhVOrYoUkSkVs6%2bPDQgTKY3T93J3hXcB4p44lqSnLmJD%2bTBT9Pb7M2ALtXu7oergMMtPCHeNk%2fjtPiKoMYrFjhMEgDtW%2f3T0ZirsjnkzqFVG1T4UZVi6aJZDmJw77uIx36BKIEF3b%2becya80l13BMuHqodkfP7WfJoJ2iFHlFS8ryudRg8JeUBcXYFyk4GgcfAwjJoVLoL7HN2YaZcHQL2289JxMadDAeYLiWgezDbG5O7eRoLA%3d%3d; path=/; secure; HttpOnly; SameSite=Lax Set-Cookie: e14Guest=1; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14Country=NL; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14Language=en; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Set-Cookie: e14TimeZone=Etc/UTC; expires=Fri, 31-Dec-9999 23:59:59 GMT; path=/; secure; HttpOnly Server-Timing: cdn-cache; desc=MISS Server-Timing: edge; dur=45 Server-Timing: origin; dur=41 Server-Timing: ak_p; desc="1758666399749_34604952_2031050784_8582_6161_4_7_-";dur=1 Strict-Transport-Security: max-age=86400 ; includeSubDomains ; preload #set ($UserId = $core_v2_user.Accessing.Id) #set ($Roles = $core_v2_utility.MakeList('Moderators', 'Almost Admins', 'Administrators')) #set ($IsAdminLike = $e14_utils.IsUserInRoleOrAdmin($UserId, $Roles)) #if($IsAdminLike == 'False') #end
Actions
Forum Thread Details
  • Replies 3 replies
  • Subscribers 3 subscribers
  • Views 1698 views
  • Users 0 members are here
Related

Resolved: Microsoft Azure Maintenance May Affect Site Performance

cstanton

The element14 Community is based on the Microsoft Azure platform.

We've received notification that there's routine maintenance in progress for the app service in West Europe which may affect the performance or availability of the element14 Community.

This will proceed for 12 hours following the creation of this post.

We have limited information on this.

Parents

  • It is too bad there wasn't a mechanism like NOTAMS used in the aviation industry, to notify members of work. A Notice to Airmen or Notice to Air Missions, is a notice filed with an aviation authority to alert aircraft pilots of potential hazards along a flight route or at a location that could affect the flight. It is really nice to know as a pilot if they are going to take down a ground site for maintenance when it is you only means of navigation.

    I suspect some members use weekends to catch up or make submissions for E14 Community work. Rather unfortunate to have it unavailable and not know about it until you are ready to use it.

  • in reply to colporteur

    There's some vague 'azure status' information here:
    https://status.azure.com/en-gb/status

    The weekend behaviour was likely due to (because of when they found the fault maybe, but also not entirely related to):

    Multiple Azure Resources - East US 2 - Mitigated (Tracking ID NMB2-ND0)

    Summary of impact: Between 02:41 and 14:30 UTC on 07 Jun 2022, a subset of customers with resources in the East US 2 region may have experienced difficulties connecting to their resources hosted in this region due to a cooling failure in one of the regions' datacenters. This impacted a subset of storage and compute resources in a single Availability Zone. Azure services with dependencies on these resources in this region may also have experienced impact. 

    Preliminary root cause: multiple Air Handling Units (AHU) failed in the impacted datacenter, leading to a sudden increase in ambient temperature. The thermal event was detected by our systems, and once temperatures reached a safety threshold, infrastructure powered down to protect hardware and data durability. The cooling failure has now been addressed and we have brought down the temperatures in the impacted area of this datacenter to normal operational levels. 

    Mitigation: After recovering the impacted AHUs, we powered storage and compute back online safely in sequence. This allowed impacted Virtual Machines to recover, as well as downstream Azure services.

    Next steps: We will continue to investigate to establish the full root cause and prevent future occurrences. Stay informed about Azure service issues by creating custom service health alerts:  for video tutorials and  for how-to documentation.

  • in reply to cstanton

    I Love IT! Reminds me of Monday morning system administration briefings at shift change. Come to think of it, no I don't want to go back there:)

Reply Children
No Data