# Tuesday, October 07, 2008
As some may have noticed, this blog has been up and down like a yo-yo for the last two weeks.

The issues are caused by the fact that I host it off the home office connection - which by and large has been solid as a rock for the last 2 years, considering the amount of traffic the site gets is fairly minimal.

I opted to be one of the first guinea pigs to try the LLU (Local Loop Unbundled) offering from Orcon on the home office - alas it has not been a pain-free experience.  I think google analytics tells the story best:

LLU_Problems.PNG

The connection got switched to LLU on around the 21st / 22nd of September - at which point my connection became a bit erratic - then it started working well enough - before going wonky again, and then completely falling over altogether on the following Saturday - at that point there was no sync.

Around Wednesday sync was restored, then Auth as well on thursday (so 5 days without any access) - the connection was looking ok at that point, but then a day or so later I started noticing that it was disconnecting every 5 to 10 minutes, then taking another 20 or so seconds to re-establish the connection, that's still happening as we speak - though they helpdesk has now raised the priority of the ticket to urgent in the hope that it might be resolved soon.

So far I've been a pretty disappointed with the alacrity of Orcons resolution process and the lack of direct contact that can be made with the LLU team.  Normally with Orcon issues get logged with the help desk, a ticket is raised, and after a couple of days you end up dealing directly with corporate support (i.e. people who know what's wrong) - this process works well, and seems to filter out those people who actually have problems related to their own hardware or lack of knowledge.

Not so with LLU, you raise a ticket, but the LLU team can't be contacted directly, and as happened with me - I had no connectivity for 5 days, and also nothing done about the issue, it just sat in the queue - and the helpdesk did not seem to know any more about the issue then I did - I end up feeling bad having to pester the helpdesk every day to find out the progress on the issue - and they keep feeding me the same line of "the LLU tech will call you once the issue has started being worked on / resolved, I'm sure they'll do a card reset 1am tomorrow" - So far nobody from Orcon has ever called me (and I'm not actually sure they ever did do a card reset, but I suspect that's probably not the issue either).

Now I'm not blogging this out of Venom - I mean all said 'n done I am guinea pigging the service to some extent and I know if I'd just stuck with my previous telecom/Orcon mix none of this would have happened - and the @Orcon folks on twitter have offered to help push the ticket through quicker which was nice (incidentally ISP available on twitter == good) - but still I just hope the issue resolution process becomes a little more robust, and I thought this might be interesting to anyone else out there considering jumping on the LLU band wagon.

So my peeves so far are:
  1. Orcon don't actually seem to be doing any follow-up - I had to do all the calling (and sitting in the queue) incidentally, 3pm is the perfect time to call their helpdesk, it's never busy.
  2. The LLU team can't be contacted - that bugs me - pestering the help desk is counter-productive for days on end, when the issue is sitting with the LLU team.  Being able to check the ticket status (with notes etc.) on-line would be have been nice as well (and saved some phone calls).
  3. The helpdesk doesn't seem to even know when the LLU team will look at an issue.  I got the distinct feeling the help desk guys knew as little as I did.
  4. No weekend support - I lost connectivity early Saturday, but the LLU team doesn't work on the weekend (or so the helpdesk told me) - this sucks - telecom have engineers working weekends, especially as Orcon are responsible for phone issues as well, I could end up with no internet or voice for an entire weekend - something I've always found Telecom very quick to respond to.  I would hope this only applies to home customers!
Hopefully these (and the technical issues I'm having) are all just teething problems and will go away as the LLU roll out continues - in the mean time forgive this blog for being partially unavailable, and my apathy in not bothering to move the site to dedicated hosting (which I do plan to do sometime this year, probably along with a change in blogging software - but I'm too busy with other things at the moment).

blog | orcon | LLU
posted @ Tuesday, October 07, 2008 12:27:33 PM (New Zealand Daylight Time, UTC+13:00)    Comments [4] | |
Search
FeedCount

Tags...
.Net (83) .Net Reactor (4) .net user groups (9) 2008SummerRoadTrip (1) ActiveRecord (1) architecture (1) architecture chat (95) ArchitectureCamp2007 (2) asp.net (1) Astoria (1) Auckland (1) base4 (9) batching (1) binsor (1) blog (4) boo (1) books (1) C# 3.0 (9) cambodia (9) CAML.Net (1) castle (40) china (8) codecamp (3) codeplex (3) dapper.net (1) DevDefined Ltd. (4) DirectShow.Net (1) DLR (1) DSL (4) EAUG (1) Enterprise Architect (5) Enterprise Architecture (1) Enterprise Library (1) F# (1) feedburner (2) first post (1) Friendster (1) generics (1) googlegears (1) hacks (3) hardware (3) hongkong (2) Horn (1) hyper-v (1) ideas (1) IoC (21) IronPython (13) IronRuby (2) jobs (1) Languages (2) laos (8) LINQ (7) LiveId (1) LLU (1) Local Government (1) MDA (1) MDD (1) microsoft (1) Model Driven Development (1) mono (1) monorail (2) Movies (1) Music (1) nDepend (1) news (1) NHibernate (3) NUnit (2) nvelocity (1) OAuth (6) office (1) OpenSocial (1) orcon (1) photos (1) php (1) PostSharp (1) powerpoint (1) presentations (1) ReSharper (1) REST (2) rhino commons (3) rhinomocks (5) Ruby (1) SaaS (1) scm (1) Screen Architect (0) SharePoint (5) silverlight (1) Splicer (4) SQL2008 (1) supcom (1) survey (1) svn (1) Syzmk (4) thailand (6) Tools (2) Tortoise SVN (1) trac (2) Travel (36) Unity (2) vietnam (7) vista (2) visual nhibernate (1) vmware (1) volta (3) VS2008 (1) WCF (3) wiki (2) wikipedia (1) Windows Server 2008 (1) windsor (6) WinForms (1) wix (2) WPF (2) xmlrpc (1) yahoo pipes (1)
Who am I?
Alex Henderson
Alex Henderson
Auckland, New Zealand
Managing Director at Dev|Defined Limited

"Self Confessed Coding Junky for 15 years"
View Alex Henderson's profile on LinkedIn
 
Mobile: +64-21-402-969
Email: bittercoder 'at' gmail 'dot' com
MSN: bittercoder_nz@hotmail
Skype: alex.devdefined
Navigation