AmberCutie's Forum
An adult community for cam models and members to discuss all the things!

Is MyFreeCams down?

  • ** WARNING - ACF CONTAINS ADULT CONTENT **
    Only persons aged 18 or over may read or post to the forums, without regard to whether an adult actually owns the registration or parental/guardian permission. AmberCutie's Forum (ACF) is for use by adults only and contains adult content. By continuing to use this site you are confirming that you are at least 18 years of age.
Status
Not open for further replies.
Oct 9, 2011
889
1,315
193
Sunny England
MFC Username
Sweetiebatman
Just wondering if it is for anyone else?

Getting stuck on the "Connecting to MyFreecams" bit

tried it on both my phone and PC
 
Still isn't working for me - guessing this is recent rather than all day? Or maybe it's localised...
Things have been working pretty fine since last night as far as I know, it might just be you/your area.
 
  • Helpful!
Reactions: Zoomer
Upvote 0
Still isn't working for me - guessing this is recent rather than all day? Or maybe it's localised...

there were like.. 4 people tweeting me telling me MFC isn't working for them, even when it was deff working.. last night. It's currently working now. I'm not sure why some people are still having problems... but it's localised.
 
  • Helpful!
Reactions: Zoomer
Upvote 0
Shall have to investigate, after all, my connection for the rest of the internet appears fine; only mfc - which takes "too long to respond".

Bah, something is definitely "odd". Shall have to dig more.

C:\Users\Mike>ping bbc.co.uk -t

Pinging bbc.co.uk [212.58.246.79] with 32 bytes of data:
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=11ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54
Reply from 212.58.246.79: bytes=32 time=12ms TTL=54

Ping statistics for 212.58.246.79:
Packets: Sent = 32, Received = 32, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 12ms, Average = 11ms

C:\Users\Mike>ping facebook.com -t

Pinging facebook.com [69.171.230.68] with 32 bytes of data:
Reply from 69.171.230.68: bytes=32 time=151ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=151ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=151ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=151ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=151ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=151ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=151ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=151ms TTL=78
Reply from 69.171.230.68: bytes=32 time=151ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=151ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=151ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78
Reply from 69.171.230.68: bytes=32 time=150ms TTL=78

Ping statistics for 69.171.230.68:
Packets: Sent = 80, Received = 80, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 150ms, Maximum = 151ms, Average = 150ms



C:\Users\Mike>ping google.co.uk -t

Pinging google.co.uk [216.58.210.35] with 32 bytes of data:
Request timed out.
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=11ms TTL=54
Request timed out.
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Request timed out.
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Request timed out.
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Request timed out.
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Request timed out.
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Request timed out.
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Request timed out.
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Request timed out.
Request timed out.
Reply from 216.58.210.35: bytes=32 time=11ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Request timed out.
Request timed out.
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=11ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Request timed out.
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=11ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=11ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Request timed out.
Reply from 216.58.210.35: bytes=32 time=9ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Request timed out.
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54
Reply from 216.58.210.35: bytes=32 time=10ms TTL=54

Ping statistics for 216.58.210.35:
Packets: Sent = 72, Received = 53, Lost = 19 (26% loss),
Reply from 216.58.210.35: Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 11ms, Average = 9ms
bytes=32

Both done at the same time - two console windows. Guess I shall dig away :D
 
Last edited:
Upvote 0
It's been down for two whole days for me, and I am based in NY on Time Warner Cable. So i am guessing it is localised or there is an issue with IP ranges.

But this is all on MFC's end. Nothing you can do about it. Maybe if they updated their technology and actually invested in the site, they would not have such issues.
 
  • Like
Reactions: HiGirlsRHot
Upvote 0
Status
Not open for further replies.