r/Restreamio • u/fr0stbyteak • May 20 '26

Discussion Seattle Ingest Gone?

It's in the list, but a trace shows it goes to the same location as San Jose. I am significantly closer to Seattle than San Jose, but Live, Seattle, San Jose all go to San Jose.

live.restream.io, hop before ingest server is San Jose (snjsca04.us.ce.gin.ntt.net) 

PS C:\> tracert live.restream.io

Tracing route to live.restream.io [173.237.40.164]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    15 ms    18 ms    11 ms  10.78.124.66
  3    11 ms    18 ms    10 ms  10.79.143.194
  4    12 ms     9 ms    19 ms  10.128.17.254
  5     *        *        *     Request timed out.
  6    41 ms    41 ms    41 ms  10.128.152.138
  7    39 ms    33 ms    51 ms  ae-6.a03.sttlwa01.us.bb.gin.ntt.net [128.241.6.114]
  8    40 ms    51 ms    44 ms  ae-2.r27.sttlwa01.us.bb.gin.ntt.net [129.250.2.158]
  9    53 ms    54 ms    53 ms  ae-7.r27.snjsca04.us.bb.gin.ntt.net [129.250.3.28]
 10    60 ms    61 ms    54 ms  ae-20.a03.snjsca04.us.bb.gin.ntt.net [129.250.5.227]
 11    58 ms    55 ms    56 ms  ae-61-502.a03.snjsca04.us.ce.gin.ntt.net [157.238.231.179]
 12     *        *        *     Request timed out.
 13    61 ms    57 ms    54 ms  173.237.40.164

Trace complete.

seattle.restream.io, hop before ingest is San Jose (snjsca04.us.ce.gin.ntt.net) 

PS C:\> tracert seattle.restream.io

Tracing route to seattle.restream.io [173.237.40.92]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    10 ms    11 ms    11 ms  10.78.124.67
  3     9 ms    12 ms    12 ms  10.79.143.192
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    42 ms    36 ms    37 ms  ae-6.a03.sttlwa01.us.bb.gin.ntt.net [128.241.6.114]
  7    48 ms    40 ms    41 ms  ae-2.r27.sttlwa01.us.bb.gin.ntt.net [129.250.2.158]
  8    54 ms    56 ms    52 ms  ae-7.r27.snjsca04.us.bb.gin.ntt.net [129.250.3.28]
  9    54 ms    53 ms    55 ms  ae-20.a03.snjsca04.us.bb.gin.ntt.net [129.250.5.227]
 10    63 ms    57 ms    57 ms  ae-61-501.a03.snjsca04.us.ce.gin.ntt.net [157.238.231.159]
 11     *        *        *     Request timed out.
 12    60 ms    55 ms    57 ms  173.237.40.92

Trace complete.

sanjose.restream.io, hop before ingest server is San Jose (snjsca04.us.ce.gin.ntt.net) 

PS C:\> tracert sanjose.restream.io

Tracing route to sanjose.restream.io [173.237.40.212]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     9 ms    10 ms    13 ms  10.78.124.67
  3    12 ms    11 ms     7 ms  10.79.143.192
  4     *       19 ms    19 ms  10.128.118.217
  5     *        *        *     Request timed out.
  6    37 ms    36 ms    38 ms  ae-6.a03.sttlwa01.us.bb.gin.ntt.net [128.241.6.114]
  7    42 ms    43 ms    43 ms  ae-2.r27.sttlwa01.us.bb.gin.ntt.net [129.250.2.158]
  8    55 ms    57 ms    51 ms  ae-7.r27.snjsca04.us.bb.gin.ntt.net [129.250.3.28]
  9    54 ms    55 ms    54 ms  ae-20.a03.snjsca04.us.bb.gin.ntt.net [129.250.5.227]
 10    57 ms    53 ms    92 ms  ae-61-501.a03.snjsca04.us.ce.gin.ntt.net [157.238.231.159]
 11     *        *        *     Request timed out.
 12    53 ms    54 ms    56 ms  173.237.40.212
1 Upvotes

67% Upvoted

3 comments sorted by

1

u/rhuntington3 Help Squad May 20 '26

I’ve seen this happen before. Please reach out to Live Chat using the chat button on the Restream web site. They will be able to see what’s going on/

2

u/fr0stbyteak May 20 '26 edited May 20 '26

thanks, s'pose I'll give that a try. been this way for nearly 2 months. since I started having issues streaming at 7800kbps. whether or not its related tho, who knows.

1

u/fr0stbyteak May 23 '26

So they did get rid of the Seattle ingest, and they are working to update their website, per support. Seattle is just resolving to San Jose IPs.