Why is site q3.jia.360.cn blocked?

[crux]

Hi,

I have smart door bell 360 D819 (https://smart.360.com/camera/d819.html) and it was working perfectly until 1st of Oct 2022. So I checked door bell log and I noticed the connection to the server failed.. sth like:

03-13 00:01:02.857 open camera config error

03-13 00:01:03.563 DefaultTimeServer is http://q3.jia.360.cn/status.php?uid=EU00U0500000446&version=D819_B_STA_20201117.0.5.50 

03-13 00:01:04.811 date_header : 
03-13 00:01:05.161 () master event [StaBind] FAILED(7)! 0 bytes, 0.235 s

And if I open that link (http://q3.jia.360.cn/status.php?uid=EU00U0500000446&version=D819_B_STA_20201117.0.5.50) directly in my mobile without wifi it returned `ok` (see attachment).

So I believe it's TPG blocked that site thus my door bell stopped working.

Can it be removed from the block list?

[Anonymous]

Hi @crux,

We do not support 3rd party smart devices we suggest to contact the manufacturer support to identify the cause of website's error and provide a troubleshooting.

Note: There is no reason for TPG to block smart device functions. 

Regards,

Hi,

I have smart door bell 360 D819 (https://smart.360.com/camera/d819.html) and it was working perfectly until 1st of Oct 2022. So I checked door bell log and I noticed the connection to the server failed.. sth like:

03-13 00:01:02.857 open camera config error 03-13 00:01:03.563 DefaultTimeServer is http://q3.jia.360.cn/status.php?uid=EU00U0500000446&version=D819_B_STA_20201117.0.5.50 03-13 00:01:04.811 date_header : 03-13 00:01:05.161 () master event [StaBind] FAILED(7)! 0 bytes, 0.235 s

And if I open that link (http://q3.jia.360.cn/status.php?uid=EU00U0500000446&version=D819_B_STA_20201117.0.5.50) directly in my mobile without wifi it returned `ok` (see attachment).

So I believe it's TPG blocked that site thus my door bell stopped working.

Can it be removed from the block list?

[david64]

Hi @crux . I looked at this last night so it may have changed since.

I did a tracert to the website and found a routing loop, see below.

Ping command fails when TTL count reaches 0.

Can you tether your computer to your mobile phone's hotspot and do the same commands. There might be a better route that TPG can use.

You could also do a test by connecting one smart device to your phone.

>tracert 101.198.193.27

Tracing route to 101.198.193.27 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  ARCHER_VR1600V [192.168.1.1]

  2     4 ms     5 ms     5 ms  10.20.26.111

  3    96 ms    97 ms    97 ms  syd-gls-har-crt3-be-100.tpg.com.au [203.221.3.33]

  4    97 ms    97 ms    96 ms  per-apt-stg-crt1-Hu-0-2-0-2.tpg.com.au [202.7.162.134]

  5    97 ms    97 ms    96 ms  sin-eqx-aye-int1-Hu-0-0-0-20.tpg.com.au [203.219.107.114]

  6   218 ms   219 ms   219 ms  c3networks2-lacp-100g.hkix.net [123.255.90.97]

  7   220 ms   221 ms   220 ms  gi100-0-0-40.br02.hkg12.pccwbtn.net [63.216.176.13]

  8   219 ms   219 ms   219 ms  63-216-176-14.static.pccwglobal.net [63.216.176.14]

  9   221 ms   221 ms   220 ms  gi100-0-0-40.br02.hkg12.pccwbtn.net [63.216.176.13]

 10   219 ms   218 ms   219 ms  63-216-176-14.static.pccwglobal.net [63.216.176.14]

 11   222 ms   220 ms   221 ms  gi100-0-0-40.br02.hkg12.pccwbtn.net [63.216.176.13]

 12   219 ms   219 ms   219 ms  63-216-176-14.static.pccwglobal.net [63.216.176.14]

 13   221 ms   221 ms   221 ms  gi100-0-0-40.br02.hkg12.pccwbtn.net [63.216.176.13]

 14   219 ms   218 ms   219 ms  63-216-176-14.static.pccwglobal.net [63.216.176.14]

>ping -n 1 101.198.193.27

Pinging 101.198.193.27 with 32 bytes of data:

Reply from 63.216.176.14: TTL expired in transit.

Ping statistics for 101.198.193.27:

    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),

>ping 63.216.176.13

Pinging 63.216.176.13 with 32 bytes of data:

Reply from 63.216.176.13: bytes=32 time=220ms TTL=243

Reply from 63.216.176.13: bytes=32 time=221ms TTL=243

Reply from 63.216.176.13: bytes=32 time=221ms TTL=243

Reply from 63.216.176.13: bytes=32 time=221ms TTL=243

Ping statistics for 63.216.176.13:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 220ms, Maximum = 221ms, Average = 220ms

>ping -n 1 63.216.176.14

Pinging 63.216.176.14 with 32 bytes of data:

Reply from 63.216.176.14: bytes=32 time=220ms TTL=54

Ping statistics for 63.216.176.14:

    Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 220ms, Maximum = 220ms, Average = 220ms

[david64]

@crux . It's happened to me a couple of times but I don't know why and haven't followed it up. You could do a Select All and copy to clipboard before posting.

At the moment, the problem seems to be with PCCW Global which owns the 2 ip addresses having the loop.

Look here for contact details: https://www.pccwglobal.com/contact-us/#asia-pacific

You can contact the Brisbane office, phone or email, or use the online form.

Just copy and paste the following into the email or form.

I am trying to reach    q3.jia.360.cn    but failing.

I have done ping command which fails with this error:

Pinging 101.198.193.27 with 32 bytes of data:
Reply from 63.216.176.14: TTL expired in transit.

I have done tracert which shows a routing loop:

  3    96 ms    97 ms    97 ms  syd-gls-har-crt3-be-100.tpg.com.au [203.221.3.33]

  4    97 ms    97 ms    96 ms  per-apt-stg-crt1-Hu-0-2-0-2.tpg.com.au [202.7.162.134]

  5    97 ms    97 ms    96 ms  sin-eqx-aye-int1-Hu-0-0-0-20.tpg.com.au [203.219.107.114]

  6   218 ms   219 ms   219 ms  c3networks2-lacp-100g.hkix.net [123.255.90.97]

  7   220 ms   221 ms   220 ms  gi100-0-0-40.br02.hkg12.pccwbtn.net [63.216.176.13]

  8   219 ms   219 ms   219 ms  63-216-176-14.static.pccwglobal.net [63.216.176.14]

  9   221 ms   221 ms   220 ms  gi100-0-0-40.br02.hkg12.pccwbtn.net [63.216.176.13]

 10   219 ms   218 ms   219 ms  63-216-176-14.static.pccwglobal.net [63.216.176.14]

 11   222 ms   220 ms   221 ms  gi100-0-0-40.br02.hkg12.pccwbtn.net [63.216.176.13]

 12   219 ms   219 ms   219 ms  63-216-176-14.static.pccwglobal.net [63.216.176.14]

The 176.13 address is in Hong Kong and 176.14 is in Virginia, USA.

Is this still an active network or is the routing incorrect from hop 6, or even incorrect from TPG on hop 5?

Here is tracert from my mobile phone using a different network which is OK.

Tracing route to 101.198.193.27 over a maximum of 30 hops

  3     *        *        *     Request timed out.
  4    27 ms    20 ms    18 ms  210.49.119.210
  5    55 ms    25 ms    17 ms  10.194.254.6
  6    34 ms    19 ms    17 ms  10.194.121.213
  7     *        *        *     Request timed out.
  8    24 ms    26 ms    28 ms  bla2-hu0-5-0.ig.optusnet.com.au [211.29.126.234]
  9   193 ms   280 ms   181 ms  203.208.177.121
 10   500 ms   317 ms   196 ms  palo-b24-link.ip.twelve99.net [62.115.8.200]
 11   248 ms   301 ms   313 ms  lax-b22-link.ip.twelve99.net [62.115.119.91]
 12   242 ms   256 ms   186 ms  chinatelecom-ic320471-las-b24.ip.twelve99-cust.net [213.248.90.121]
 13   336 ms   317 ms   315 ms  218.30.55.17
 14   236 ms   309 ms   205 ms  218.30.44.70
 15     *        *        *     Request timed out.
 16   193 ms   390 ms   220 ms  101.198.193.27

[crux]

@david64 

I sent email to PCCW last week - they didn't response to me but the good news is today I see route to `http://q3.jia.360.cn/` works again and my door bell is now back to normal!

Thanks lot for your support!