@cowboybuddah: What triggered it is appointment data going up to your Google Calendar server and then syncing back down to your iOS device. The way this bug works, is that it causes any appointment created on an iOS device to acquire the time zone that the clock of your hosted calendar server is set to...which is GMT on most Google and Exchange servers. It then transposes your appointments to whatever that time zone is.
This is discussed at length in the thread but every few weeks a new bunch of people find this thread and they go about trying to "figure this out" from scratch. I'm not trying to be snarky etc... I am trying to save you and others who might not scroll more than one or two pages back some time.
This bug is not generated by Google. It is generated by iOS. How do I know that for sure you ask? I don't use Google for anything and I have this bug. I use Exchange. I reported this to AppRiver, my Exchange host in early November. They spent a bunch of time working on it with Apple Engineering Tech Support and Apple confirmed...in writing...that this is a bug in iOS 8. Of course some other guy at Apple says it is a "feature" and this is the "expected behavior," but if you read through this thread one thing that will become evident is that Apple's internal communications among its tech support staff are p1ss poor.
Here's an article AppRiver wrote that explains exactly what is going on:
http://blog.appriver.com/2014/12/ios-8-calendar-events-display-dual-time-zones/
Follow this thread for a few days and watch new people show up and proclaim the "Found the FIX!!!" and that they are "pretty sure this is not a bug in iOS 8 but it is a bug with Google Calendar."
Sorry that it came back for you, but your experience simply further confirms this is a bug in iOS. The only people who can fix it are the engineers at Apple, and several of us have been informed they are in fact working on a fix.
Keep your fingers crossed that the fix is part of iOS 8.1.3 which is coming out any day now....