Is sf.gov down or not working?

What happened to sf.gov, why did the website go down and not work? Here you can see who else is having the same problem with sf.gov, as well as possible solutions. According to our statistics, the following most often do not work: Website, Login, Account, Mobile App.

Current status: No failures

At the moment, according to our data, sf.gov is working fine, but single failures are possible. If sf.gov does not work for you, then report your problem and write a comment.
Add comment

What to do if the site sf.gov is not available? Try our guide.

sf.gov outage reports in the last 24 hours

sf.gov - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.
  • No registration required.
  • Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
  • Active links in the text of the message are not published, but displayed in plain text.
  • It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.

Technical information

Main page title:
City and County of San Francisco
Main page description:
Find services and information from the City and County of San Francisco.
Protocol:
https
Status code:
200
Page size:
75.6 KB
Response time:
1.864sec.
IP:
199.48.133.250
Response headers:
content-type: text/html; charset=UTF-8
content-length: 77498
connection: close
server: nginx
cache-control: must-revalidate, no-cache, private
date: Tue, 01 Oct 2024 02:19:01 GMT
x-drupal-dynamic-cache: UNCACHEABLE
content-language: en
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
expires: Sun, 19 Nov 1978 05:00:00 GMT
x-generator: Drupal 10 (https://www.drupal.org)
surrogate-key: config:block_emit_list config:block.block.404footer config:block.block.404pagenotfound config:block.block.sfgovsearchblock_3 config:block.block.department_children_emit_listing_block config:block.block.department_related_emit_listing_block config:block.block.department_services_emit_listing_block config:block.block.sfgovpl_account_menu user:0 config:block.block.sfgovpl_content config:block.block.sfgovpl_help config:block.block.sfgovpl_local_actions config:block.block.sfgovpl_local_tasks config:block.block.sfgovpl_page_title node:2 config:block.block.topic_services_emit_listing_block config:block.block.footerbottom config:block.block.gtranslate config:block.block.sfgovpl_branding config:block.block.sfgovpl_breadcrumbs config:block.block.sfgovpl_main_menu config:block.block.sfgovpl_messages config:block.block.sfgovpl_powered config:block.block.sfgovpl_tools config:block.block.sfgovsearchblock config:block.block.sfgovpl_footer config:block.block.sfgovsearchblock_2 config:block.block.views_block__events_block_1 config:block.block.views_block__news_block_2 config:block.block.webform config:webform.webform.was_this_page_helpful_ webform:was_this_page_helpful_ config:webform.settings config:extlink.settings config:google_tag_container_emit_list config:google_tag.container.GTM-NQB74NJ.6628a000c0fc02.37593912 block_view config:system.menu.footer-bottom node:10446 node:10448 config:system.menu.footer node:10438 node:10452 config:core.entity_form_display.webform_submission.was_this_page_helpful_.add config:antibot.settings config:honeypot.settings node_view paragraph_view paragraph:280 config:paragraphs.settings paragraph:15852 paragraph:16955 node:2692 user:10436 paragraph:15851 node:12510 user:10256 paragraph:15850 node:182 user:1629 paragraph:15849 node:679 paragraph:39516 node:5355 user:10841 paragraph:15846 node:195 user:1 paragraph:15845 config:filter.format.sf_basic_html paragraph:15844 node:176 paragraph:15834 node:189 paragraph:15843 node:175 paragraph:15842 node:178 paragraph:15841 node:1471 paragraph:15840 node:4380 user:107 paragraph:15839 node:663 paragraph:15838 node:7905 paragraph:15836 node:179 paragraph:15835 node:1470 paragraph:15837 node:174 paragraph:15833 paragraph:15832 node:169 paragraph:656 paragraph:655 config:views.view.news node_emit_list node:15149 node:15152 node:6084 node:15180 user:11314 user:11473 user:10225 user:11191 paragraph:2205 paragraph:2204 config:views.view.services node:260 node:162 node:19 node:2048 node:25 node:4 node:5946 node:226 node:768 node:2573 node:6049 node:16 node:767 node:769 config:field.storage.node.field_description user:197 user:10756 user:845 paragraph:4793 paragraph:94344 media:36409 group_content_emit_list:plugin:group_media:audio group_content_emit_list:plugin:group_media:file group_content_emit_list:plugin:group_media:image group_content_emit_list:plugin:group_media:video local_task config:workflows.workflow.editorial config:system.menu.main config:system.site rendered http_response config:user.role.anonymous config:csp.settings
access-control-allow-origin: *
vary: Accept-Encoding
x-cache: Miss from cloudfront
via: 1.1 01abec7ece24959c09067a58477de9ee.cloudfront.net (CloudFront)
x-amz-cf-pop: AMS1-P2
x-amz-cf-id: mHLsB4-fYhAW4plUqU6FY57qY1PwI9dMg1wtA0dTfBoEXOXk1cS9Kg==

SEO headers

h1 Stay safe and keep cool during the heat wave
h2 Services
h2 News
h2 Elected Officials
h3 Board of Supervisors
h3 Elected Officers
h2 Footer menu
h2 Footer Bottom

How to solve problems with sf.gov

Errors on the sf.gov website can be either on the server side or on your side (client side). If there is practically nothing to be done about errors on the server side (it remains only to wait for the site to work again), then with errors on the client side it is possible to solve the problem with the availability of sf.gov on your own.