Fastmail system down - Page 3

XB77 · 29 Jan 2004, 02:24 AM

At 10:20AM PT (USA) no IMAP access. OE: Unknown error. Couple of minutes previous, sloow web access, manual POPLink worked.

How can one tell which server one is accessing for IMAP or web access?

XB77 · 29 Jan 2004, 02:27 AM

At 10:26AM PT still no IMAP access (despite server change Jeremy just mentioned).

Jeremy Howard · 29 Jan 2004, 02:29 AM

That's odd. We're not aware of any problems. Can try run fasttest? ( www.fastmail.fm/fasttest.exe )

XB77 · 29 Jan 2004, 02:33 AM

Okay, ran it. Now what--you want me to PM you a copy? Or does the copy button do that automatically? Also, looking it over I see that it is trying to do some pings which I have blocked by my firewall. I can make myself pingable and re run FastTest if that would be better. Advise please. IMAP still not accessible at 10:37AM PT (USA). OE: "Unknown error."

Jeremy Howard · 29 Jan 2004, 02:37 AM

PM me a copy please.

**Sherry** · 29 Jan 2004, 02:39 AM

Quote:

Originally posted by XB77
How can one tell which server one is accessing for IMAP or web access?

When you login, somewhere in the URL it will show mail, mail1, mail2 etc.

Sherry

reuben · 29 Jan 2004, 02:39 AM

the best ever will be when the new server is faster and better than the old ones ever were

that will be the best ever.

but now we're all having imtermittent issues with our email and we're curious and the "morning" is a long time forward here in the states

so 3 cheers for communicating with us about it.

i suggest longer debug phase for next server upgrade?

perhaps putting it on beta and encouraging people there to give it their all to highlight problems so as to avoid server going completely mysteriously down during prime business hours in the NY time zone?

also a little redundancy goes a long way.... (RAM is pretty easy to come by and defective RAM is not altogether totally rare - can it be tested before use?)

again. 3 cheers for being on it.

Jeremy Howard · 29 Jan 2004, 02:40 AM

Actually, it doesn't show that at the moment. We're redirecting everyone to the same server while we fix the hardware problem.

Jeremy Howard · 29 Jan 2004, 02:42 AM

Quote:

Originally posted by reuben
also a little redundancy goes a long way.... (RAM is pretty easy to come by and defective RAM is not altogether totally rare - can it be tested before use?)

NVRAM is not the same as RAM - not easy to come by!

But certainly we would have liked to test for longer. We brought the servers online faster than we planned, to resolve the performance problems of the last few days.

Jeremy Howard · 29 Jan 2004, 02:43 AM

Quote:

Originally posted by mac'd
Is there a Macintosh version of Fasttest in the works?

No - sadly, I don't have a Mac.

Jeremy Howard · 29 Jan 2004, 02:44 AM

Quote:

Originally posted by XB77
Okay, ran it. Now what--you want me to PM you a copy?

Thanks for the PM. It shows no problems with IMAP connectivity from your location - can you please try another IMAP client and see if you have the same problem? If so, can you try the 'account problems' link on the FastMail.FM home page?

reuben · 29 Jan 2004, 02:45 AM

excellent! thank you jeremy!

XB77 · 29 Jan 2004, 02:54 AM

10:47AM PT IMAP accessible now. FWIW back when I was getting "unknown errors," IMAP was accessible from MyRealBox (for a change). Ironically I migrated to paid service at FM due to unreliability of MRB.

10:53 FM IMAP really popping at moment. Last few days/week or more typically had to click more than once to get update--first click an error, click another folder then back for update.

David · 29 Jan 2004, 03:23 AM

Quote:

Originally posted by mac'd
Jeremy,

Is there a Macintosh version of Fasttest in the works?

You could try this. And run as a shell script. It works on OS X. 10.2 (I copied it from some stuff elvey jotted down) a long time ago.

#/bin/sh
uname
dig www.google.com
dig www.fastmail.fm
dig www.dot.fm .....
traceroute www.fastmail.fm
traceroute www.zoneedit.com

---------------------------

This is the output.

Darwin

; <<>> DiG 8.3 <<>> www.google.com
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUERY SECTION:
;; www.google.com, type = A, class = IN

;; ANSWER SECTION:
www.google.com. 13m45s IN CNAME www.google.akadns.net.
www.google.akadns.net. 3m12s IN A 216.239.33.99

;; Total query time: 65 msec
;; FROM: h24-68-24-69 to SERVER: default -- 64.59.160.13
;; WHEN: Wed Jan 28 11:09:12 2004
;; MSG SIZE sent: 32 rcvd: 83

; <<>> DiG 8.3 <<>> www.fastmail.fm
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUERY SECTION:
;; www.fastmail.fm, type = A, class = IN

;; ANSWER SECTION:
www.fastmail.fm. 9m17s IN A 66.111.4.62

;; Total query time: 45 msec
;; FROM: h24-68-24-69 to SERVER: default -- 64.59.160.13
;; WHEN: Wed Jan 28 11:09:12 2004
;; MSG SIZE sent: 33 rcvd: 49

; <<>> DiG 8.3 <<>> www.dot.fm .....
;; res_nmkquery: buffer too small

traceroute to www.fastmail.fm (66.111.4.62), 30 hops max, 40 byte packets
1 24.68.24.1 (24.68.24.1) 21.652 ms 85.02 ms 18.561 ms
2 rd1cv-ge3-1.gv.shawcable.net (64.59.161.130) 19.581 ms 20.12 ms 16.109 ms
3 rc1bb-atm0-1-1.vc.shawcable.net (66.163.76.93) 95.163 ms 20.422 ms 22.105 ms
4 rc1ar-pos14-0.ed.shawcable.net (66.163.76.162) 34.633 ms 97.044 ms 35.417 ms
5 rc1nr-pos13-0.wp.shawcable.net (66.163.76.77) 54.512 ms 83.008 ms 53.256 ms
6 rc1sh-pos13-0.mt.shawcable.net (66.163.76.73) 128.324 ms 78.081 ms 75.846 ms
7 rc1hu-pos7-0.ny.shawcable.net (66.163.76.158) 133.156 ms 90.278 ms 87.564 ms
8 nyi.net (198.32.160.87) 134.83 ms 90.259 ms 88.169 ms
9 delancyst.nyi.net (64.90.175.1) 130.036 ms 89.109 ms 92.983 ms
10 astorpl-cs-30-nyi.net (66.111.15.204) 138.971 ms 85.347 ms 87.822 ms
11 www.fastmail.fm (66.111.4.62) 137.865 ms 87.481 ms 87.522 ms
traceroute to www.zoneedit.com (64.21.143.23), 30 hops max, 40 byte packets
1 24.68.24.1 (24.68.24.1) 113.453 ms 20.479 ms 22.026 ms
2 rd1cv-ge3-1.gv.shawcable.net (64.59.161.130) 30.857 ms 104.145 ms 21.122 ms
3 rc1bb-atm0-1-1.vc.shawcable.net (66.163.76.93) 22.067 ms 20.875 ms 70.358 ms
4 rc1ar-pos14-0.ed.shawcable.net (66.163.76.162) 43.496 ms 36.557 ms 33.704 ms
5 rc1nr-pos13-0.wp.shawcable.net (66.163.76.77) 113.549 ms 50.225 ms 56.585 ms
6 rc1sh-pos13-0.mt.shawcable.net (66.163.76.73) 140.124 ms 79.618 ms 75.866 ms
7 rc1hu-pos7-0.ny.shawcable.net (66.163.76.158) 141.158 ms 88.029 ms 88.162 ms
8 nyiix.ge-2-2-0.gbr1.nyc.nac.net (198.32.160.20) 145.743 ms 85.121 ms 88.031 ms
9 0.so-0-2-0.gbr1.nwr.nac.net (209.123.11.126) 140.952 ms 90.798 ms 88.008 ms
10 0.so-7-3-0.gbr2.oct.nac.net (209.123.11.58) 140.281 ms 90.827 ms 87.256 ms
11 fa0-0.core1.pwebtech.com (207.99.8.198) 146.045 ms * *
12 fa0-0.core1.pwebtech.com (207.99.8.198) 150.755 ms * *
13 fa0-0.core1.pwebtech.com (207.99.8.198) 218.5 ms * 109.355 ms
14 * fa0-0.core1.pwebtech.com (207.99.8.198) 117.196 ms *
15 * * fa0-0.core1.pwebtech.com (207.99.8.198) 113.017 ms
16 * * *
17 * fa0-0.core1.pwebtech.com (207.99.8.198) 114.571 ms *
18 * * fa0-0.core1.pwebtech.com (207.99.8.198) 116.154 ms
19 * * *
20 fa0-0.core1.pwebtech.com (207.99.8.198) 226.571 ms * *
21 fa0-0.core1.pwebtech.com (207.99.8.198) 228.183 ms * 114.013 ms
22 * fa0-0.core1.pwebtech.com (207.99.8.198) 115.46 ms *
23 fa0-0.core1.pwebtech.com (207.99.8.198) 230.2 ms * *
24 * * fa0-0.core1.pwebtech.com (207.99.8.198) 121.366 ms
25 * fa0-0.core1.pwebtech.com (207.99.8.198) 169.502 ms *
26 fa0-0.core1.pwebtech.com (207.99.8.198) 231.515 ms * *
27 * * *
28 fa0-0.core1.pwebtech.com (207.99.8.198) 232.398 ms * *
29 * * *
30 * * *

**ReuvenNY** · 29 Jan 2004, 03:38 AM

Jeremy has posted a new thread - an update: http://www.emaildiscussions.com/...threadid=18724 In order to avoid confusion, let's address all the issues on that thread.

29 Jan 2004, 02:24 AM	#31
XB77 Essential Contributor Join Date: Dec 2002 Location: Los Angeles Posts: 365	At 10:20AM PT (USA) no IMAP access. OE: Unknown error. Couple of minutes previous, sloow web access, manual POPLink worked. How can one tell which server one is accessing for IMAP or web access?

29 Jan 2004, 02:27 AM	#32
XB77 Essential Contributor Join Date: Dec 2002 Location: Los Angeles Posts: 365	At 10:26AM PT still no IMAP access (despite server change Jeremy just mentioned).

29 Jan 2004, 02:29 AM	#33
Jeremy Howard Ultimate Contributor Join Date: Sep 2001 Location: Australia Posts: 11,501	That's odd. We're not aware of any problems. Can try run fasttest? ( www.fastmail.fm/fasttest.exe )

29 Jan 2004, 02:33 AM	#34
XB77 Essential Contributor Join Date: Dec 2002 Location: Los Angeles Posts: 365	Okay, ran it. Now what--you want me to PM you a copy? Or does the copy button do that automatically? Also, looking it over I see that it is trying to do some pings which I have blocked by my firewall. I can make myself pingable and re run FastTest if that would be better. Advise please. IMAP still not accessible at 10:37AM PT (USA). OE: "Unknown error."

29 Jan 2004, 02:37 AM	#35
Jeremy Howard Ultimate Contributor Join Date: Sep 2001 Location: Australia Posts: 11,501	PM me a copy please.

29 Jan 2004, 02:39 AM	#37
reuben Essential Contributor Join Date: Jun 2002 Posts: 240	the best ever will be when the new server is faster and better than the old ones ever were that will be the best ever. but now we're all having imtermittent issues with our email and we're curious and the "morning" is a long time forward here in the states so 3 cheers for communicating with us about it. i suggest longer debug phase for next server upgrade? perhaps putting it on beta and encouraging people there to give it their all to highlight problems so as to avoid server going completely mysteriously down during prime business hours in the NY time zone? also a little redundancy goes a long way.... (RAM is pretty easy to come by and defective RAM is not altogether totally rare - can it be tested before use?) again. 3 cheers for being on it.

29 Jan 2004, 02:40 AM	#38
Jeremy Howard Ultimate Contributor Join Date: Sep 2001 Location: Australia Posts: 11,501	Actually, it doesn't show that at the moment. We're redirecting everyone to the same server while we fix the hardware problem.

29 Jan 2004, 02:45 AM	#42
reuben Essential Contributor Join Date: Jun 2002 Posts: 240	excellent! thank you jeremy!

29 Jan 2004, 02:54 AM	#43
XB77 Essential Contributor Join Date: Dec 2002 Location: Los Angeles Posts: 365	10:47AM PT IMAP accessible now. FWIW back when I was getting "unknown errors," IMAP was accessible from MyRealBox (for a change). Ironically I migrated to paid service at FM due to unreliability of MRB. 10:53 FM IMAP really popping at moment. Last few days/week or more typically had to click more than once to get update--first click an error, click another folder then back for update.

29 Jan 2004, 03:38 AM	#45
ReuvenNY Moderator Join Date: Mar 2002 Location: New York Posts: 4,259	Jeremy has posted a new thread - an update: http://www.emaildiscussions.com/...threadid=18724 In order to avoid confusion, let's address all the issues on that thread.