Is sanfranciscobayferry.com down or not working?

What happened to sanfranciscobayferry.com, why did the website go down and not work? Here you can see who else is having the same problem with sanfranciscobayferry.com, 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, sanfranciscobayferry.com is working fine, but single failures are possible. If sanfranciscobayferry.com does not work for you, then report your problem and write a comment.
Add comment

What to do if the site sanfranciscobayferry.com is not available? Try our guide.

sanfranciscobayferry.com outage reports in the last 24 hours

sanfranciscobayferry.com - 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:
San Francisco Bay Ferry | San Francisco Bay Ferry
Protocol:
https
Status code:
200
Page size:
44.2 KB
Response time:
0.736sec.
IP:
23.185.0.2
Response headers:
connection: close
content-length: 45323
cache-control: max-age=60, public
content-language: en
content-type: text/html; charset=UTF-8
etag: W/"1727810158"
expires: Sun, 19 Nov 1978 05:00:00 GMT
last-modified: Tue, 01 Oct 2024 19:15:58 GMT
link: <https://sanfranciscobayferry.com/take-the-ferry>; rel="canonical", <https://sanfranciscobayferry.com/node/1>; rel="shortlink"
permissions-policy: interest-cohort=()
server: nginx
strict-transport-security: max-age=300
x-content-type-options: nosniff
x-drupal-cache: HIT
x-drupal-dynamic-cache: MISS
x-frame-options: SAMEORIGIN
x-generator: Drupal 9 (https://www.drupal.org)
x-pantheon-styx-hostname: styx-fe2-a-5cc68c7f44-5gc5d
x-styx-req-id: 59fc3ebb-804f-11ef-9a8e-7621fbb415b8
x-ua-compatible: IE=edge
date: Tue, 01 Oct 2024 23:46:17 GMT
x-served-by: cache-chi-kigq8000054-CHI, cache-ams2100133-AMS
x-cache: MISS, MISS
x-cache-hits: 0, 0
x-timer: S1727826377.167086,VS0,VE147
vary: Accept-Encoding, Cookie, Cookie, Cookie
age: 0
accept-ranges: bytes
via: 1.1 varnish, 1.1 varnish
DNS records:
A address23.185.0.2
ttl300
AAAA address2620:12a:8001::2
ttl300
AAAA address2620:12a:8000::2
ttl300
MX exchangemx1.emailsrvr.com
priority10
MX exchangemx2.emailsrvr.com
priority20
NS valuens1.hover.com
NS valuens2.hover.com
TXT entriesv=spf1 include:emailsrvr.com ~all
TXT entriesv=spf1 include:mail.zendesk.com ?all
TXT entriesgoogle-site-verification=FgCHBbM57Ulbw77Z8CLQdCyXNPlCeDerOgMTExDKOEs
SOA nsnamens1.hover.com
hostmasterdnsmaster.hover.com
serial1720469362
refresh1800
retry900
expire604800
minttl300

SEO headers

h2 News
h2 News
h2 Main navigation

How to solve problems with sanfranciscobayferry.com

Errors on the sanfranciscobayferry.com 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 sanfranciscobayferry.com on your own.