In this context, “Exception: forbidden” almost certainly means the web server is returning a 403 Forbidden error: the server is actively denying access to that page or resource. This usually reflects a permissions, security, or configuration rule on the server side (or sometimes blocking of certain networks or clients), not something the visitor can fix locally.
Public information does not show a documented, site‑wide outage for state.gov tied specifically to this error message, so it is unclear whether the problem is only with the “Restoring America’s Global Health Leadership” page or with a broader part of the site. The only reliable way to tell is to try other state.gov URLs (such as the homepage or releases index) from your own connection; if those load normally, the issue is likely limited to that page or section, but if they return the same “technical difficulties / forbidden” message, it indicates a wider technical or access‑control problem.
Yes. The press statement “Restoring America’s Global Health Leadership” is listed in the State Department’s releases archive as a press statement dated December 22, 2025, by Secretary of State Marco Rubio. However, the primary state.gov page currently returns the same “technical difficulties / Exception: forbidden” error, so the full text may need to be accessed later via the same URL or the State Department’s web/FOIA archives once the issue is resolved.
State Department indexing pages indicate that “Restoring America’s Global Health Leadership” is a press statement, not a speech transcript, and it is attributed to Marco Rubio, Secretary of State, dated December 22, 2025. That means the page is expected to contain a written press statement authored in the Secretary’s name, rather than live remarks; there is no indication that this specific URL combines both remarks and a separate press release.
Because 403/“forbidden” errors and the accompanying “technical difficulties” message are usually caused by server‑side configuration or access‑control issues, there is no fixed wait time. In practice, you can: (1) try again after some hours or the next day to see if State’s web team has resolved it; and (2) if the error persists for more than a day or two, contact the State Department’s public contact channel (e.g., the general contact form or Public Communication Division) and provide the exact URL and error message so they can escalate it to their web administrators.
The primary official source for this announcement is the State Department’s own releases archive at state.gov, which currently hosts but is not properly serving the page. If the site remains inaccessible, possible alternate official or near‑official channels include: (1) State Department social media accounts (e.g., @StateDept or @StateDeptSpox) where new press statements are often linked; (2) email subscription lists or RSS feeds for State Department press releases; and (3) the State Department’s web or FOIA archives, which preserve copies of official statements and may later provide a PDF or archived HTML of this press statement once the technical problem is resolved.