[183257] in North American Network Operators' Group
RE: Google Apps for ISPs -- Lingering fallout
daemon@ATHENA.MIT.EDU (Josh Luthman)
Mon Aug 24 08:33:27 2015
X-Original-To: nanog@nanog.org
In-Reply-To: <BY1PR0501MB1462CD4C372F9736031B078FB4620@BY1PR0501MB1462.namprd05.prod.outlook.com>
Date: Mon, 24 Aug 2015 08:33:23 -0400
From: Josh Luthman <josh@imaginenetworksllc.com>
To: Ryan Finnesey <ryan@finnesey.com>
Cc: nanog <nanog@nanog.org>, Gary Greene <ggreene@minervanetworks.com>
Errors-To: nanog-bounces@nanog.org
Initially no. After a while yes.
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
On Aug 24, 2015 1:44 AM, "Ryan Finnesey" <ryan@finnesey.com> wrote:
> Was Google charging ISPs for this service?
>
> Cheers
> Ryan
>
>
> -----Original Message-----
> From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Gary Greene
> Sent: Tuesday, August 18, 2015 2:18 PM
> To: Shawn L <shawnl@up.net>
> Cc: nanog <nanog@nanog.org>
> Subject: Re: Google Apps for ISPs -- Lingering fallout
>
> You=E2=80=99ll need to escalate this with Google. If the front-end suppor=
t team
> cannot help, move up the chain as far as you can. It should eventually
> reach the PM that worked on the turn-down of that service and get some
> action.
>
> --
> Gary L. Greene, Jr.
> Sr. Systems Administrator
> IT Operations
> Minerva Networks, Inc.
> Cell: +1 (650) 704-6633
>
>
>
>
> > On Aug 18, 2015, at 10:39 AM, Shawn L <shawnl@up.net> wrote:
> >
> >
> > I know there are others on this list who used Google Apps for ISPs and
> recently migrated off (as the service was discontinued).
> >
> > We have had several cases where the user had a YouTube channel or Picas=
a
> photo albums, etc. that they created with their Google Apps for ISPs
> credentials. Now that the service is gone, those channels and albums sti=
ll
> exist but the users are unable to login to them or manage them in any way
> because it tells them that their account has been disabled.
> >
> > Of course, Google had been un-responsive to all of our (and the
> customer's) inquiries about how to fix this.
> >
> > Has anyone else run into this and found a way around it?
> >
> > thanks
> >
> >
> > Shawn
> >
>
>
