Is RFC3767 down or not working?

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

Current status: No failures

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

Securely outage reports in the last 24 hours

User reports by hour (UTC), last 24 hours

Hour
Weight 0 0 0 0 0 0
Hour
Weight 0 0 0 0 0 0
Hour
Weight 0 0 0 0 0 0
Hour
Weight 0 0 0 0 0 0

Total weight in 24 hours: 0 Busiest hour: 20:00 UTC (weight 0)

How this score compares

Current 24-hour weight is 0. Warnings start at 20, Failed at 50. Median services on this language today is 0.

Other services in this category

Official links

  • Facebook: https://www.facebook.com/171432316317408
  • Twitter: http://www.twitter.com/Securly

About Securely

Securely, also known as RFC 3767 or the Securely Available Credentials Protocol, is an instance of a request for comments publication. It falls under the categories of app, login, and website.
Securely (RFC 3767) defines the Securely Available Credentials Protocol, an IETF request for comments publication. On this page you can check whether the service behind it is behaving normally. We track connection errors, login failures, and problems reaching the website. Reports update as users submit them, so statuses reflect current conditions rather than assumptions.
Securely is associated with RFC 3767, the Securely Available Credentials Protocol. The published material describes a framework for moving credentials securely between devices and parties. As a service row here, it covers the app, the login flow, and the website. When something breaks, it is usually one of three things: the site does not load, authentication requests time out, or credential retrieval fails partway through. These can look similar from the outside, so we group them by type on the status board. Before reporting a fault, check your own connection first. Confirm your login details are current, clear the app cache if the site loads but sign-in stalls, and try a different network if you can. If the status page shows an active incident, you do not need to file a separate report for the same problem.

Questions

Is Securely down right now?

According to reports on this page, Securely looks fine for most people. Isolated failures still happen — report yours if you are stuck.

When was the last mass outage?

We do not have a recorded mass outage for Securely yet.

What does Securely do?

It is tied to RFC 3767, the Securely Available Credentials Protocol, which describes how credentials can be transferred securely. The service row here covers its app, login flow, and website.

What should I include in an outage report?

Describe what you see: an error message, a loading timeout, or a failed sign-in. Note the device and network you are using. Avoid guessing at causes; the report text you submit is what we work from.

Securely - error and failure reports, troubleshooting methods

Is RFC3767 down or not working?
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.