Is bram.us down or not working?

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

What to do if the site bram.us is not available? Try our guide.

bram.us outage reports in the last 24 hours

bram.us - 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:
Bram.us – A rather geeky/technical weblog, est. 2001, by Bramus
Protocol:
https
Status code:
200
Page size:
120.5 KB
Response time:
1.169sec.
IP:
176.62.167.56
Response headers:
server: nginx
date: Sat, 05 Oct 2024 12:48:35 GMT
content-type: text/html; charset=UTF-8
transfer-encoding: chunked
connection: close
x-xss-protection: 1; mode=block
expect-ct: max-age=7776000, enforce
access-control-allow-origin: null, *
access-control-allow-methods: GET,PUT,POST,DELETE, GET,PUT,POST,DELETE
access-control-allow-headers: Content-Type, Authorization, Content-Type, Authorization
x-content-security-policy: default-src 'self'; img-src *; media-src * data:;, img-src *; media-src * data:;
x-content-type-options: nosniff
content-security-policy: report-uri https://www.bram.us
referrer-policy: strict-origin-when-cross-origin
cross-origin-embedder-policy-report-only: unsafe-none; report-to="default"
cross-origin-embedder-policy: unsafe-none; report-to="default"
cross-origin-opener-policy-report-only: same-origin; report-to="default"
cross-origin-opener-policy: same-origin-allow-popups; report-to="default"
cross-origin-resource-policy: cross-origin
x-frame-options: SAMEORIGIN
permissions-policy: accelerometer=(), autoplay=(), camera=(), fullscreen=*, geolocation=(self), gyroscope=(), microphone=(), payment=*
feature-policy: display-capture 'self'
x-permitted-cross-domain-policies: none, none
strict-transport-security: max-age=31536000; includeSubDomains; preload, max-age=31536000
link: <https://www.bram.us/wp-json/>; rel="https://api.w.org/"
vary: Accept-Encoding

SEO headers

h1 Bram.us
h2 Benchmarking the performance of CSS @property
h2 Solved by CSS Scroll-Driven Animations: hide a header when scrolling down, show it again when scrolling up.
h2 The CSS Podcast 089: View Transitions
h2 Observing Style Changes (2024.09.25 @ devs.gent)
h2 Feature detecting Scroll-Driven Animations with @supports: you want to check for animation-range too
h2 A better capturing mode for View Transitions
h2 Animate to height: auto; (and other intrinsic sizing keywords) in CSS
h2 Introducing @bramus/caniuse-cli, a CLI tool for “Can I Use …”
h2 Introducing @bramus/style-observer, a MutationObserver for CSS
h2 Feature detect CSS @starting-style support
h2 Posts navigation
h2 About Bram.us
h2 Stay up-to-date
h2 Archives
h2 Search

How to solve problems with bram.us

Errors on the bram.us 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 bram.us on your own.