I can't reproduce this... it's quite fast from both home (Norway) or here from London. Can you make a traceroute perhaps?

Try again a bit later.
It should be said that most of the time the response is ok - even a bit slow - but still ok.

But then for longer periods the response are wery slow.

The initial request is very slow, all later requests are fine.
Probably some DNS issues :|

I dont think its a DNS issue because FireFox says "Waiting for no2.php.net" - that means as far as i can see that the DNS lookup is finished.

This has been a problem for me and several others for quite some time.
And it doesn't appear to be DNS-related.

--------
$ time wget http://no2.php.net/time
--23:36:30--  http://no2.php.net/time
           => `time'
Resolving no2.php.net... 128.39.198.38
Connecting to no2.php.net|128.39.198.38|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]

    [<=>] 248,613      361.21K/s

23:37:29 (360.18 KB/s) - `time' saved [248613]


real    0m58.703s
user    0m0.010s
sys     0m0.000s
--------

This one is from home, but the story is the same when I try from no.php.net as well as from several other hosts in norway and abroad. Practically all of the 58 seconds were spent waiting for connect. And as Hannes points out, it's just the initial request. At least that's how I experience it.

This problem is still present.
Today the connection times out more often than it gives any results.

I have tried to change my default mirron on /my.php but it still connects to no2.php.net.

Are there any hope that this is going to be fixed? 
Because its wery frustrating waiting for the dox in several minutes while you are coding.

Changing your preferences in my.php should work fine, if it doesn't please open another report about.

Derick: Do you have _any_ idea whatsup with no2?

I've no idea why... and I can't reproduce it either.

Almost no lag-time to and from the United States either, nor can I 
reproduce any error.  Perhaps more of a local network issue than a 
mirror problem.

It magically started to work just fine few weeks ago

I have been annoyed by the same problem over the few past years -- including today.

The no2.php.net mirror is slightly unstable, at least when searching in the function index (that's what I normally do). Sometimes it takes 30-60 seconds for the server to respond.

It's a real PITA when I try to quickly look up a function signature or documentation through the http://php.net/<function_name>, and it always(?) choose the unstable (no2.php.net) mirror!

So how about changing the defaults to the most stable mirror, or maybe round-robin them?

I know the user can change this under my.php.net but I like sane and working defaults.

I have hit the same problem from multiple ISP (Telenor and Ventelo).

I can confirm this.

Function look-up on this mirror is extremely slow at times and has been this way for several years.

There's no reason to believe this is network related in any way as the server accepts the request immediately but can take up to 1 minute before returning the result.