Any computer experts here?

Because after all this time, I'm still having trouble getting Serebii to work properly. I found out about the tracert command in the command prompt, so I gave it a spin during one of those moments when nothing would load, and here's what it looked like (my personal IP doesn't appear anywhere, so I think I can show it all uncensored (translation to English done manually):

Tracing serebii.net [69.65.41.131] over a maximum of 30 hops:

  1    <1 ms     2 ms     1 ms  192.168.0.1
  2     8 ms     7 ms     9 ms  172.16.0.1
  3    15 ms    10 ms    12 ms  172.30.13.85
  4    15 ms    11 ms    11 ms  172.30.249.29
  5    13 ms    12 ms    13 ms  te-9-2.car2.Montreal2.Level3.net [4.59.178.89]
  6    35 ms    35 ms    35 ms  te-2-4.er1.Chi4.Servernap.net [66.252.3.161]
  7    36 ms    35 ms    38 ms  po-13.csr1.Chi3.Servernap.net [66.252.0.65]
  8    35 ms    34 ms    35 ms  po-103.ddr2.Chi3.Servernap.net [66.252.0.138]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
...
 30     *        *        *     Request timed out.

Trace complete.

The last IP address I see there, 66.252.0.138, seems to belong to the ISP that hosts Serebii's site. So since I can get a packet this far, the problem would be on their end, except I seem to be the only one that's having problems. So I have absolutely no idea. Is my ISP involved somehow? Odds are no one else here has Cogeco as ISP, so I can't even ask anyone to load tons of stuff on Serebii and see if it holds up. And my family's with Bell, so there goes that.

Just for kicks, here's what things look like when I can actually get Serebii to load something (that is, when it's been a while since I've last tried to load anything):

Tracing serebii.net [69.65.41.131] over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     8 ms     7 ms     7 ms  172.16.0.1
  3    11 ms    15 ms    16 ms  172.30.13.85
  4    12 ms    12 ms    11 ms  172.30.249.29
  5    12 ms    13 ms    12 ms  te-9-2.car2.Montreal2.Level3.net [4.59.178.89]
  6    34 ms    36 ms    33 ms  te-2-4.er1.Chi4.Servernap.net [66.252.3.161]
  7    37 ms    36 ms    34 ms  po-13.csr1.Chi3.Servernap.net [66.252.0.65]
  8    34 ms    35 ms    35 ms  po-103.ddr2.Chi3.Servernap.net [66.252.0.138]
  9   103 ms    35 ms    35 ms  serebii.net [69.65.41.131]

Trace complete.

Yep, as an extra kick in the nuts it turns out it's the very last step in the process that's not getting done.