WHEN: Thursday September 11, 2025 6:30am - 7:30am IMPACT: Server fs01 and key systems dependent fs01 will be rebooted.  Relevant services will be unavailable during the reboot. Total outage time is expected to be about 10-15 minutes. (innovation-web01, its-web04, ssh1, dev-mariadb1, dev-mariadb2, dev-mariadb3, prod-mariadb1, mariadb2, mariadb3, alb3) WHAT/WHY: Reboots needed to apply routine Linux system patches. WHO: Patrick Canole

WHEN: Thursday September 18, 2025 3:00AM - 3:30 AM IMPACT: Server INFRA-SQL-PROD will be rebooted.  Relevant services will be unavailable during the reboot. Total outage time is expected to be about 10-15 minutes. WHAT/WHY: Reboots needed to apply routine Windows updates. WHO: Patrick Canole

ServiceNow - Maintenance Communication Record Created COMM2187912 Short Description SSL certificate notification: Be informed Affected Instance uritest, urisdbx, rhody, uridev SSL certificate notification Be informed • No downtime • September 2025 We like to keep things secure. So, twice a year we update the SSL certificate supporting your ServiceNow instances in our data centers. The last update was performed in April 2025. Here's what you can expect This is a change to the *.service-now.com SSL certificate only. It will not affect the DigiCert Root Certificate Authority, which does not expire until 2030. If your organization does not hard-code SSL certificates, this update will not affect your ability to connect to your instance, and no action is needed from you. If you have hard-coded our leaf certificate into your infrastructure, you will need to manually update the certificate. Here are some common cases where hard-coded SSL certificates may be found: You use a proxy server to access your ServiceNow instance. The proxy may have the current SSL leaf certificate hard-coded into the proxy software. You have inbound integrations that connect to your ServiceNow instance. Some examples of these can be found here: ServiceNow Product Documentation: List of Available Integrations. Keep in mind: We strongly discourage hard-coding SSL certificates. Hard-coding creates a dependency on specific certificates and requires you to run a manual update when we change them. Please note, ServiceNow reserves the right to rotate certificates without customer notification in response to a security need, should one arise. Read RFC5280 for additional information. The certificate update is applied at the data center level, so we are prevented from modifying the scheduled date and time. Maintenance details: Update of the *.service-now.com SSL Certificate Host data centers: BWI/IAD/PHX/SJC Service impact: None expected Maintenance start time: Thursday, September 18, 2025 16:00 (PDT) Thursday, September 18, 2025 19:00 (EDT) Maintenance end time: Friday, September 19, 2025 01:00 (PDT) Friday, September 19, 2025 04:00 (EDT) Here's what we need you to do Check with your network administrators to see if there are any hard-coded leaf certificates for ServiceNow on your systems. If you do not have hard-coded certificates, no further action is needed. We will perform the maintenance at the date and time listed above. If you have integrations, caching, or proxy servers that have hard-coded the current ServiceNow SSL certificate, then you will need to update to the new SSL certificate. Visit KB0563633 to obtain a copy of the new leaf certificate so you can do a manual update in conjunction with our update of the SSL leaf certificate. Questions? Review KB0563633 for additional details regarding this update. We are here to help. If you have any questions before the maintenance window, please log in to reply directly to this Communication Record. If you have any questions during or after the maintenance window, please open a Case or visit the Customer Support - Contact Us knowledge article for contact information in your region. Maintenance Start : 2025-09-18 16:00:00 US/Pacific | 2025-09-18 23:00:00 UTC Maintenance End : 2025-09-19 01:00:00 US/Pacific | 2025-09-19 08:00:00 UTC

CHG67054779 Patching notification Review • No downtime • September 2025 We will apply new security patches in August 2025 on your ServiceNow^® instances. They contain critical fixes that improve the safety of your environment. No performance or functional fixes are included in this release. Here's what you can expect We will patch your instance(s) to the Now Platform^® versions shown below. rhody (prod)  CHG67120103 Here's what we need you to do You’ll soon receive Change (CHG) notifications with more details on your August patching dates. Sub-production instances will be scheduled in the first two weeks of the month, production instances will be scheduled 14 days later. Please take a look at them and do the following: Review the scheduled time for each CHG to confirm it works for your organization. You can reschedule until August 31, if needed. If you have questions or run into problems when you try to reschedule, contact us by entering a comment into the CHG and our dedicated team will get back to you. Please note: Unless you reschedule your CHG, we will patch your instance on the date and time listed in the CHG. Need Help with Your Patching Schedule? If you need assistance or encounter issues with your Patching Change, leave a comment on this Change Request (CHG). Our dedicated team will respond promptly. For more details about communicating through Change Requests, refer to the following Knowledge Base article: KB1644913. We really appreciate you Thank you for staying up to date with patching. It's the best way to provide your organization with productive, reliable experiences. Questions? For more information on managing your ServiceNow instance upgrades, review KB0541128 and KB0995477. For additional resources, please reference our FAQs and follow us on the Upgrades and Patching Community. Important: Keep Your Contact Information Updated Be sure to keep your company contacts updated to ensure you continue to receive these notifications.