ferlores / npm-status-www Goto Github PK

It seems that this happens relatively often. I've wasted a ton of time trying to figure out why I can't run npm adduser, but it seems to be a registry problem that occurs regularly. Maybe the npm status page could check for that as well.

https://registry.npmjs.org/-/user/org.couchdb.user:sigfriedgold

{"error":"not_found","reason":"missing"}

NPM Status often reports green when there are outtages

http://stats.pingdom.com/d50hxzpzk7x4/650599

As I type this, one registry server is up, the other is down. The status page apparently hits the load balancer, so what it reports all depends on which system the LB refers it to.

The status page can have gotten lucky, and seen the up server, while someone actually trying to use this stuff gets directed to the server that is down (gee thanks load balancer) and is sad face..

Is the twitter robot on strike?

It would be good to besides the web has an API that returns a JSON with the state (of both registry and the web) to query from a Chrome extension or Firefox addon

And I can confirm that the website is up.

Round colored balls are really an ambiguous sort of thing, especially if any of our users suffer from red/green color blindness. (a terrible UX often borrowed from Jenkins)

Color is fine if we want to use it, but it should be combined with icons that are unique, instead of all the same (e.g. round balls)

For example if we used thumbs (up, sideways, down) or something like a Green Check for good, a red 'circle-with-slash' for down, and um something else for yellow.. (question mark?)

btw: for great dev tool to 'see' the screen as a color blind person would, see 'colororacle.org'