mailinator blocked?

[#1]

I use mailinator.com every now and then as a spam trap, but I suddenly could not access it any more yesterday. Looking at http://www.isitdownrightnow.com/mailinator.com.html it doesn't seem to be down generally. Can anyone else on plusnet see it? I tried restarting the browser, which made no difference, but haven't yet gone for a full reboot flush DNS caches etc. - not much point if for some reason it's been blocked on plusnet for everyone.

[#2]

http://www.mailinator.com/
This works but the link you posted had .html on the end which screwed it

[#3]

Thanks Oldjim - no the link you provided doesn't work for me, DNS cache flush here we come...
(the link I posted was to another site to show that mailinator itself wasn't down)

[#4]

Caches flushed and restarted computer, but still cannot access mailinator.com - very odd... call to the helpdesk I suppose?

[#5]

Can you post a tracert
This is what I get

Tracing route to mailinator.com [207.198.106.56]
over a maximum of 30 hops:
  1    1 ms    80 ms    99 ms  192.168.1.254
  2    43 ms    33 ms    32 ms  lo0-central10.pcl-ag01.plus.net [195.166.128.182]
  3    32 ms    32 ms    33 ms  link-b-central10.pcl-gw02.plus.net [212.159.2.162]
  4    32 ms    32 ms    32 ms  194.core.access.plus.net [212.159.0.194]
  5    39 ms    36 ms    32 ms  ae1.ptw-cr02.plus.net [195.166.129.2]
  6    32 ms    31 ms    35 ms  ae2.ptw-cr01.plus.net [195.166.129.4]
  7    32 ms    32 ms    34 ms  195.66.224.156
  8    *        *        *    Request timed out.
  9    *        *        *    Request timed out.
10    *        *        *    Request timed out.
11    *        *        *    Request timed out.
12    *        *        *    Request timed out.
13    *        *        *    Request timed out.
14    *        *        *    Request timed out.
15  198 ms  197 ms  198 ms  mailinator.com [207.198.106.56]

[#6]

I can get to http://mailinator.com and it crashes Firefox (maybe Linux specific problem)!
[tt]traceroute to mailinator.com (207.198.106.56), 30 hops max, 52 byte packets
1  192.168.0.1 (192.168.0.1)  3.513 ms
2  lo0-central10.pcl-ag06.plus.net (195.166.128.187)  27.454 ms
3  link-a-central10.pcl-gw01.plus.net (212.159.2.180)  25.256 ms
4  212.core.access.plus.net (212.159.0.212)  25.827 ms
5  ae1.ptw-cr01.plus.net (195.166.129.0)  24.468 ms
6  195.66.224.156 (195.66.224.156)  24.076 ms
7  *
8  *
9  *
10  *
11  *
12  *
13  *
14  mailinator.com (207.198.106.56)  191.090 ms[/tt]
Edit: Firefox crashing was due to buggy fontconfig 2.10.94

[#7]

OK here:
Running Firefox 23.0.1 on windows vista.

[#8]

Works fine for me.

[#9]

I get a very odd traceroute
traceroute to mailinator.com (207.198.106.56), 64 hops max, 52 byte packets
1  dsldevice.lan (192.168.1.254)  11.244 ms  97.440 ms  99.973 ms
2  lo0-central10.ptn-ag03.plus.net (195.166.128.192)  9.139 ms  9.950 ms  8.961 ms
3  link-a-central10.ptn-gw01.plus.net (212.159.2.136)  8.536 ms  36.148 ms  8.458 ms
4  108.core.access.plus.net (212.159.0.108)  8.244 ms  10.832 ms  8.274 ms
5  195.66.224.156 (195.66.224.156)  8.262 ms  8.059 ms  8.219 ms
6  * * *
7  * * *
8  * * *
9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * dsldevice.lan (192.168.1.254)  80.015 ms !H
27  dsldevice.lan (192.168.1.254)  52.617 ms !H  99.236 ms !H  99.953 ms !H

[#10]

I get much the same up to 27, then *** to 30
But the webpage works here.

[#11]

I don't suppose there's anything in the router event log relating to 207.198.106.56? You could try "gateway hopping", disconnect then reconnect from the router web interface, to see if a different plusnet gateway works any different.

[#12]

Yes, disconnect and reconnect worked... for a few minutes, but then mailinator stopped working again... very odd indeed.