```json
{
    "title": "Opera Web Site: Hello? Anyone home?",
    "url": "https://performancezen.com/2006/02/18/opera-web-site-hello-anyone-home/",
    "datePublished": "2006-02-18",
    "dateModified": "2006-02-18",
    "language": "en-US",
    "description": "As a Web performance analyst, this is the sort of graph that melts your mind and makes you want to scream at the gods|goddesses to rain a plague of locusts…",
    "author": "spierzchala",
    "publisher": "Performance Zen"
}
```

# Opera Web Site: Hello? Anyone home?

As a Web performance analyst, this is the sort of graph that melts your mind and makes you want to scream at the gods|goddesses to rain a plague of locusts on the offending System|Network|Web Site Administrators.

[http://www.flickr.com/photos/spierzchala/101037386/](http://www.flickr.com/photos/spierzchala/101037386/)
***Click for a larger version***

This is a classic display of the "*run in circles, scream and shout*" problem identification and resolution process.

One-half of the Opera Web servers at [http://www.opera.com/](http://www.opera.com/) are not responding.

50%.

They have three separate public IP addresses, and it is clear that behind those IPs are many more NAT|VIP machines that respond to requests.

Did I mention that one-half of the machines at all three IP addresses are not responding to HTTP requests?

Has anyone at Opera noticed this?

Sometimes I feel like even the echoes aren't listening anymore.

Technorati Tags: [GrabPERF](http://technorati.com/tag/GrabPERF), [Web performance](http://technorati.com/tag/Web%20performance), [Opera](http://technorati.com/tag/Opera), [Opera Web browser](http://technorati.com/tag/Opera%20Web%20browser), [www.opera.com](http://technorati.com/tag/www.opera.com)