Earlier quoted context omitted.
Coming from australia and not familiar at all with Webpass... is the latency low? ie. could people use this for gaming internet connections?
Yes. It's point to point wireless to a building and Ethernet from there. No real latency issue there.
Google Fiber agrees to acquire Webpass
11–20 of 135 posts
Re: Google Fiber agrees to acquire Webpass
#12Earlier quoted context omitted.
My webpass is already 1 Gbps symmetric. If yours is less, it's a per-building upgrade (so maybe with additional capital they'd do that in more places) and may not be feasible. Disclosure: I work at Google (but not on Fiber).
Coming from australia and not familiar at all with Webpass... is the latency low? ie. could people use this for gaming internet connections?
Re: Google Fiber agrees to acquire Webpass
#13Earlier quoted context omitted.
My webpass is already 1 Gbps symmetric. If yours is less, it's a per-building upgrade (so maybe with additional capital they'd do that in more places) and may not be feasible. Disclosure: I work at Google (but not on Fiber).
Coming from australia and not familiar at all with Webpass... is the latency low? ie. could people use this for gaming internet connections?
Re: Google Fiber agrees to acquire Webpass
#14Earlier quoted context omitted.
Yes. It's point to point wireless to a building and Ethernet from there. No real latency issue there.
Curious what they're using for backhaul wireless links if they're offering 1 gbps service. Not many solutions can handle that kind of speed.
Re: Google Fiber agrees to acquire Webpass
#15Webpass has only been doing fiber for 10 months [0], as far as I know the bulk of their customers in SF are on fixed wireless. I'm discouraged by this announcement - now it seems there's zero chance of widespread Google Fiber in SF. [0] https://webpass.net/blog/fiber-is-here
Disclosure edit: I'm a current Webpass P2P wireless customer. I was literally about to switch away from Webpass to another P2P wireless solution (we have a site evaluation next Monday) because Webpass has been unreliable for us lately. I'm really curious what, if anything, this means for Webpass and Google Fiber in SF.
Re: Google Fiber agrees to acquire Webpass
#16So will Webpass be faster now?
My webpass is already 1 Gbps symmetric. If yours is less, it's a per-building upgrade (so maybe with additional capital they'd do that in more places) and may not be feasible. Disclosure: I work at Google (but not on Fiber).
My building is on 500mbit Webpass and things get pretty dire at peak times.
Re: Google Fiber agrees to acquire Webpass
#17Earlier quoted context omitted.
My webpass is already 1 Gbps symmetric. If yours is less, it's a per-building upgrade (so maybe with additional capital they'd do that in more places) and may not be feasible. Disclosure: I work at Google (but not on Fiber).
It's more the interconnection with the rest of the Internet than the building uplink... :) My building is on 500mbit Webpass and things get pretty dire at peak times.
Re: Google Fiber agrees to acquire Webpass
#18Earlier quoted context omitted.
My webpass is already 1 Gbps symmetric. If yours is less, it's a per-building upgrade (so maybe with additional capital they'd do that in more places) and may not be feasible. Disclosure: I work at Google (but not on Fiber).
Coming from australia and not familiar at all with Webpass... is the latency low? ie. could people use this for gaming internet connections?
Re: Google Fiber agrees to acquire Webpass
#19Earlier quoted context omitted.
My webpass is already 1 Gbps symmetric. If yours is less, it's a per-building upgrade (so maybe with additional capital they'd do that in more places) and may not be feasible. Disclosure: I work at Google (but not on Fiber).
Coming from australia and not familiar at all with Webpass... is the latency low? ie. could people use this for gaming internet connections?
No login, no metering, no shaping.
Example latency:
admin@RT-AC5300-E6A0:/tmp/home/root# ping -c 5 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=55 time=3.526 ms
64 bytes from 8.8.8.8: seq=1 ttl=55 time=3.559 ms
64 bytes from 8.8.8.8: seq=2 ttl=55 time=3.547 ms
64 bytes from 8.8.8.8: seq=3 ttl=55 time=3.518 ms
64 bytes from 8.8.8.8: seq=4 ttl=55 time=3.584 ms
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 3.518/3.546/3.584 msRe: Google Fiber agrees to acquire Webpass
#20Wow, unexpected. I used Webpass when I was in SF and was very happy with the quality of their service, so them getting more capital to expand is a great development.