[AusNOG] Reverse Trace routes needed 103.12.159.0/24

[Cameron Murray]

This is how we get to you:

Tracing route to acs-asn-gw.acs.net.au [103.12.159.1]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.79.254
  2     2 ms     1 ms     1 ms  little.router [27.122.119.214]
  3     3 ms     3 ms     2 ms  v899.bigger.router [103.17.250.218]
  4    18 ms    17 ms    21 ms  as4826.nsw.ix.asn.au [218.100.52.6]
  5    18 ms    18 ms    17 ms  bundle-100.cor03.syd03.nsw.vocus.net.au
[114.31.192.44]
  6    18 ms    18 ms    17 ms  ten-1-2-0.bdr03.syd03.nsw.vocus.net.au
[114.31.192.53]
  7    16 ms    19 ms    15 ms  as24093.cust.bdr01.syd03.nsw.vocus.net.au
[114.31.200.134]
  8    18 ms    17 ms    33 ms  125-253-41-46.dyn.ver.bigair.net.au
[125.253.41.46]
  9    94 ms    86 ms   111 ms  203.132.77.86
 10    28 ms    22 ms    23 ms  acs-asn-gw.acs.net.au [103.12.159.1]

Trace complete.

Do you maintain your own peering or does your upstream do this for you?

Regards

Cameron

On Fri, Feb 3, 2017 at 8:53 AM, Benjamin Ricardo <ben.ricardo at acs.net.au>
wrote:

> Hi All,
> I’ve not used this list before so be kind if I breach any sort of
> protocols ☺
>
> Our IP resource 103.12.159.0/24 ASN134791 has been unreachable to a lot
> of locations as of 9am yesterday morning... we're dying here.
>
> Long short is I need traces to 103.12.159.1 from  lots of different
> networks (preferably people peered with Equinix as I believe this is where
> the issue is)
>
> Not sure how this list works.... but this is what I need to help this
> fault to keep moving.
>
> Thanks
>
> Ben
> Australian Computer Solutions
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20170203/07a7fd4b/attachment-0001.html>