Deprecated: Creation of dynamic property wpdb::$categories is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/wp-db.php on line 668

Deprecated: Creation of dynamic property wpdb::$post2cat is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/wp-db.php on line 668

Deprecated: Creation of dynamic property wpdb::$link2cat is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/wp-db.php on line 668

Deprecated: Return type of WP_Theme::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-theme.php on line 554

Deprecated: Return type of WP_Theme::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-theme.php on line 595

Deprecated: Return type of WP_Theme::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-theme.php on line 535

Deprecated: Return type of WP_Theme::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-theme.php on line 544

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/comment-template.php on line 1739

Deprecated: wp_getimagesize(): Implicitly marking parameter $image_info as nullable is deprecated, the explicit nullable type must be used instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/media.php on line 5006

Deprecated: Return type of WP_REST_Request::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/rest-api/class-wp-rest-request.php on line 960

Deprecated: Return type of WP_REST_Request::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/rest-api/class-wp-rest-request.php on line 980

Deprecated: Return type of WP_REST_Request::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/rest-api/class-wp-rest-request.php on line 992

Deprecated: Return type of WP_REST_Request::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/rest-api/class-wp-rest-request.php on line 1003

Deprecated: Return type of WP_Block_List::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-block-list.php on line 151

Deprecated: Return type of WP_Block_List::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-block-list.php on line 175

Deprecated: Return type of WP_Block_List::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-block-list.php on line 164

Deprecated: Return type of WP_Block_List::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-block-list.php on line 186

Deprecated: Return type of WP_Block_List::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-block-list.php on line 138

Deprecated: Return type of WP_Block_List::offsetExists($index) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-block-list.php on line 75

Deprecated: Return type of WP_Block_List::offsetGet($index) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-block-list.php on line 89

Deprecated: Return type of WP_Block_List::offsetSet($index, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-block-list.php on line 110

Deprecated: Return type of WP_Block_List::offsetUnset($index) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-block-list.php on line 127

Deprecated: Return type of WP_Block_List::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-block-list.php on line 199

Deprecated: Jetpack::setup_xmlrpc_handlers(): Implicitly marking parameter $xmlrpc_server as nullable is deprecated, the explicit nullable type must be used instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/class.jetpack.php on line 939

Deprecated: Automattic\Jetpack\Connection\Manager::setup_xmlrpc_handlers(): Implicitly marking parameter $xmlrpc_server as nullable is deprecated, the explicit nullable type must be used instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/src/class-manager.php on line 110

Deprecated: Creation of dynamic property Automattic\Jetpack\Connection\Manager::$error_handler is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/src/class-manager.php on line 80

Deprecated: Creation of dynamic property WPCOM_REST_API_V2_Endpoint_Instagram_Gallery::$is_wpcom is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/_inc/lib/core-api/wpcom-endpoints/class-wpcom-rest-api-v2-endpoint-instagram-gallery.php on line 23

Deprecated: Creation of dynamic property WPCOM_REST_API_V2_Endpoint_Mailchimp::$wpcom_is_wpcom_only_endpoint is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/_inc/lib/core-api/wpcom-endpoints/class-wpcom-rest-api-v2-endpoint-mailchimp.php on line 17

Deprecated: Creation of dynamic property WPCOM_REST_API_V2_Endpoint_Tweetstorm_Gather::$wpcom_is_wpcom_only_endpoint is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/_inc/lib/core-api/wpcom-endpoints/class-wpcom-rest-api-v2-endpoint-tweetstorm-gather.php on line 21

Deprecated: Creation of dynamic property WPCOM_REST_API_V2_Endpoint_Tweetstorm_Gather::$is_wpcom is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/_inc/lib/core-api/wpcom-endpoints/class-wpcom-rest-api-v2-endpoint-tweetstorm-gather.php on line 22

Deprecated: Creation of dynamic property WPCOM_REST_API_V2_Endpoint_Gutenberg_Available_Extensions::$wpcom_is_site_specific_endpoint is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/_inc/lib/core-api/wpcom-endpoints/gutenberg-available-extensions.php on line 20

Deprecated: Creation of dynamic property WPCOM_REST_API_V2_Endpoint_Memberships::$wpcom_is_wpcom_only_endpoint is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/_inc/lib/core-api/wpcom-endpoints/memberships.php on line 23

Deprecated: Creation of dynamic property WPCOM_REST_API_V2_Endpoint_Memberships::$wpcom_is_site_specific_endpoint is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/_inc/lib/core-api/wpcom-endpoints/memberships.php on line 24

Deprecated: Creation of dynamic property WPCOM_REST_API_V2_Endpoint_Subscribers::$wpcom_is_wpcom_only_endpoint is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/_inc/lib/core-api/wpcom-endpoints/subscribers.php on line 15

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/extensions/blocks/podcast-player/podcast-player.php on line 157

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/extensions/blocks/podcast-player/podcast-player.php on line 157

Deprecated: Creation of dynamic property Automattic\Jetpack\Sync\Queue::$random_int is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/class-queue.php on line 38

Deprecated: Creation of dynamic property Automattic\Jetpack\Sync\Queue::$random_int is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/class-queue.php on line 38

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/widgets/migrate-to-core/image-widget.php on line 195

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/widgets/migrate-to-core/gallery-widget.php on line 56

Deprecated: Creation of dynamic property Publicize_UI::$in_jetpack is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/publicize.php on line 53

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/calypsoify/class-jetpack-calypsoify.php on line 128

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/calypsoify/class-jetpack-calypsoify.php on line 129

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/calypsoify/class-jetpack-calypsoify.php on line 133

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/calypsoify/class-jetpack-calypsoify.php on line 134

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/calypsoify/class-jetpack-calypsoify.php on line 135

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/simple-payments/simple-payments.php on line 219

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/simple-payments/simple-payments.php on line 220

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/simple-payments/simple-payments.php on line 227

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/simple-payments/simple-payments.php on line 229

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/simple-payments/simple-payments.php on line 231

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/simple-payments/simple-payments.php on line 248

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/simple-payments/simple-payments.php on line 249

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/simple-payments/simple-payments.php on line 267

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/simple-payments/simple-payments.php on line 268

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/simple-payments/simple-payments.php on line 270

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/simple-payments/simple-payments.php on line 271

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/simple-payments/simple-payments.php on line 273

Deprecated: Using ${var} in strings is deprecated, use {$var} instead in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/simple-payments/simple-payments.php on line 275

Deprecated: Creation of dynamic property WPCOM_Widget_Goodreads::$shelves is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/widgets/goodreads.php on line 33

Deprecated: DateTime::__construct(): Passing null to parameter #1 ($datetime) of type string is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/script-loader.php on line 348

Deprecated: Creation of dynamic property WP_Block_Type::$plan_check is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-block-type.php on line 333

Deprecated: Creation of dynamic property WP_Block_Type::$plan_check is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-block-type.php on line 333

Deprecated: Creation of dynamic property WP_Block_Type::$plan_check is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-block-type.php on line 333

Deprecated: Creation of dynamic property WP_Block_Type::$plan_check is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-block-type.php on line 333

Deprecated: Creation of dynamic property WP_Block_Type::$plan_check is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-block-type.php on line 333

Deprecated: Creation of dynamic property WP_Block_Type::$plan_check is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/class-wp-block-type.php on line 333

Deprecated: Creation of dynamic property Jetpack_Shortcode_Unavailable::$shortcodes is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-content/plugins/jetpack/modules/shortcodes/unavailable.php on line 19

Warning: Cannot modify header information - headers already sent by (output started at /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/wp-db.php:668) in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Warning: Cannot modify header information - headers already sent by (output started at /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/wp-db.php:668) in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Warning: Cannot modify header information - headers already sent by (output started at /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/wp-db.php:668) in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Warning: Cannot modify header information - headers already sent by (output started at /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/wp-db.php:668) in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Warning: Cannot modify header information - headers already sent by (output started at /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/wp-db.php:668) in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Warning: Cannot modify header information - headers already sent by (output started at /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/wp-db.php:668) in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/wp-db.php on line 3030

Warning: Cannot modify header information - headers already sent by (output started at /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/wp-db.php:668) in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1648

Warning: Cannot modify header information - headers already sent by (output started at /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/wp-db.php:668) in /homepages/34/d43362328/htdocs/ydontu/blog/wp-includes/rest-api/class-wp-rest-server.php on line 1648
{"id":1217,"date":"2007-09-27T19:40:54","date_gmt":"2007-09-27T18:40:54","guid":{"rendered":"http:\/\/www.whydontyou.org.uk\/blog\/2007\/09\/27\/pipex-terrible-isp\/"},"modified":"2008-09-10T21:30:19","modified_gmt":"2008-09-10T20:30:19","slug":"pipex-terrible-isp","status":"publish","type":"post","link":"http:\/\/www.whydontyou.org.uk\/blog\/2007\/09\/27\/pipex-terrible-isp\/","title":{"rendered":"Pipex – Terrible ISP"},"content":{"rendered":"

Long rant – if you are reading this on Planet Atheism<\/a> \/ Planet Humanism<\/a> (or just aren’t interested) and you don’t want to know about my troubles with a UK based ISP please skip this<\/a> \ud83d\ude42 If you know anyone thinking of getting a new ISP, simply tell them to avoid Pipex at all costs.<\/p>\n

My problems with Pipex<\/a> continue unabated. I am in the process of trying to move away from them and get Sky Broadband but I am hitting hurdle after hurdle.<\/p>\n

Following on from the fiasco where I had an entire month without internet connection, despite repeated false promises by the customer services staff and the only offer Pipex could make to placate me was to promise me an extra months connection for free – when this free month will be is anyone’s guess, I am still being billed each month – the connection still sucks. Pipex technical support have reached new levels of incompetence and it is getting to the point where I am tempted to simply cancel this phone line and get a new one…<\/p>\n

<\/p>\n

Since my internet connection returned at the start of this month it has been snail like. Internet banking is a hit and miss affair, as it will often time out before I get the chance to do anything. After a few days, when this reached unbearable, I started looking at the router settings etc. In doing this, I noticed that the router was reporting the connection was 576kbps when previously it had been saying 8192kbps.<\/p>\n

Blimey, this shocked me. I use the internet a lot, for a lot of things, so I had been willing to pay over the average rate to go with an ISP that is reported to have excellent service, excellent reliability and very fast speeds. It turns out, I am paying over the odds for an ISP that has erratic service, terrible reliability, terrible customer services, terrible technical support and is barely faster than a good dial up connection. Needless to say I was incensed that I am paying their top rate for a service worse than any they describe on their site – when I signed up, you had the choice of three speeds “Up to 2mb” was the cheapest and a fraction of what I am paying.<\/p>\n

\"Thinkbroadband.com<\/a>Obviously, being a rational person, I was keen to get my facts straight and I tried several speed tester services (such as Thinkbroadband.com<\/a> and www.speeedtester.bt.com<\/a>), trying each on different days and so on. As you can see from the graph, Thinkbroadband confirms my suspicions that the connection had deteriorated massively. The Speedtester site had similar results, reporting:<\/p>\n

Test1 comprises of Best Effort Test: -provides background information.
\nIP profile for your line is – 500 kbps<\/strong>
\nDSL connection rate: 288 kbps<\/strong>(UP-STREAM) 576 kbps<\/strong>(DOWN-STREAM)
\nActual IP throughput achieved during the test was – 411 kbps<\/strong><\/p><\/blockquote>\n

Jeepers, I thought to myself. Obviously this can’t be right! From thinkbroadband, you can see that the connection was never lightning – although it was certainly fast enough for any of my needs – and now it is terminally slow. Sending large emails (something which happens quite a bit) seems like it would be faster to write the binary code for the file on a letter and post it via Royal Mail. Seriously, it is that bad.<\/p>\n

Anyway, on 08 Sep I’d had enough of this and I emailed Pipex’s tech support. By a miracle, I had a reply on 12 Sep giving me a list of steps to check out. Four days is good for Pipex. This read as follows:<\/p>\n

Thank you for your email<\/p>\n

The speed of a connection can be affected by a variety of things. One of
\nthe biggest culprits in slowing a connection down is the P2P application.
\nP2P or Peer To Peer applications such as Kazaa, BearShare, LimeWire, WinMX,
\neMule and eDonkey have gained world wide popularity and use.<\/p>\n

If you are sure that there are no P2P applications running and that there
\nare no issues with your firewall then we would ask that you to perform the
\nfollow diagnostics to eliminate your equipment from causing this issue.<\/p>\n

Hardware<\/p>\n

We first need to make sure that your hardware is not affecting the speed at
\nwhich the ADSL runs at<\/p>\n

1) Please make sure you’re not running any P2P applications or
\ndata-streaming websites and to make sure you have scanned for viruses
\nrecently<\/p>\n

2) Remove all other devices from the line (such as any phones, fax machines,
\nsky boxes, alarm systems and this includes downstairs and upstairs)<\/p>\n

3) Swap the filters which your modem\/router uses<\/p>\n

4) If you have a spare modem\/router then please try this to eliminate the
\nmodem or router being responsible. Also for Modems please make sure that you
\nhave the latest drivers update and if if you use a router, please make sure
\nyou have the lastest firmware version.<\/p>\n

5) Take the circuit back to a basic circuit. That’s just one PC (not a whole
\nnetwork) and from the back of that you have 1 modem or router device which
\ngoes through an ADSL micro filter and then directly into the BT master
\nsocket (without an extension cable)<\/p>\n

Running Speed tests<\/p>\n

Once you have ruled out you’re hardware from being responsible there is a
\nspeed test we need you to run so we can present the results to BT in order
\nfor this matter to be investigated:<\/p>\n

Connect to the internet using a BT username (speedtest@speedtest_domain) and
\nusing ‘adsl’ as your password and then to run 6 speedtests at different
\ntimes of the day on a website at this address http:\/\/217.35.209.142 or
\nhttp:\/\/217.32.105.42 or www.speedtester.bt.com (Please note: you cannot view
\nwebpages or use your e-mails whilst using this username)<\/p>\n

If you do have problems using the speedtest@speedtest_domain username,
\nplease go ahead and use your original Pipex Log on details, but you will
\nhave to Note down the Date and Time you ran the TESTS, and the Results
\nobtained.<\/p>\n

Once you have done this, please call us on 0845 077 2455 and we can escalate
\nthe fault to BT as we are unable to do this via e-mail.<\/p>\n

Please feel free to contact us if you require further assistance.<\/p><\/blockquote>\n

I don’t have a problem with the “teaching to suck eggs” bit at the start, they have to go through the basics. I was a touch annoyed that they were asking me to redo each of the tests I had already done though. As I had already done tests on Speedtester, I telephoned customer support and was informed it was “important” that I did the tests using the speedtest log on data and the tests needed to be carried out over a “few consecutive days.” Eventually I gave up trying to resist and decided to comply with their demands. Due to the nature of my work, it was only today I managed to comply with the “consecutive days” tests.<\/p>\n

Armed with the test data – all showing the connection never once went past 499kbps – I rang technical support again. After another 20 minutes listening to the most bored person in the world saying “we value your call” (seriously, ring up just to hear the irony in the way she says it), I got through to a tech support person. Now the fun began.<\/p>\n

When asked what the problem was, I explained the whole deal, how the connection died all of August and how the speedtester was showing a snail like service. This prompted the “technician” to try and explain to me about how I should try a different filter or change the WiFi router to see if that helped. When I asked how that would affect the speedtest website (which tests the line, not your PC) he was a bit stumped. He recovered quickly though, and moved on to asking me to carry out the speed tests by logging in as speedtest@speedtest_domain.<\/p>\n

I have tried this numerous times and each time I can “log” in (sort of) but the speedtest websites just return a “timed out” error – obviously not a good sign. I tried to provide the technical support person with my speedtest results, but he cut me off fairly quickly and said they needed to comprise of six tests over a 24 hour period. I was flabbergasted. No amount of protest would make him accept my test data from Speedtest. Instead, he said I had to carry them out again – “a few tonight, some in the morning, some in the middle of the day and a few in the evening then call back.” Quite how I am supposed to do this from work is beyond me, and he could offer no alternative. If I don’t do the 24 hours worth of tests, he claims the problem wont be escalated<\/em> to BT. Amazing. The hideous cynic inside me thinks this was nothing more than an attempt to get me off the line so he could deal with an easier customer. Once more, however, it seems that every problem falls to BT and as Pipex informed me last time, they have no service level agreement so they feel totally absolved of any blame. Despite this, Pipex will not allow me to go direct to BT and require everything be done via them. Does this seem fair? Are they having their cake, eating it and<\/strong> loaning it out to others?<\/p>\n

Well, anyway, I am now left with having to carry out another 24 hours worth of tests. Needless to say, I am not going to carry them out – I am going to aggregate my previous data and claim that is the current data. The upshot of this whole sorry mess is that I can’t even migrate to a new ISP until the line is restored back to its previous status – any other provider would simply end up providing me with a 0.5meg connection.<\/p>\n

I really, really do hate Pipex now.<\/p>\n

To really rub salt into the wounds, when you visit Pipex’s website it is covered with blurbs about how it is in the “Top 5 Broadband providers” and how “98% of customers are pleased with its speeds” and so on. This may be great for attracting new customers, but when you are a customer suffering the ills of the world it does nothing but infuriate. Add to this the almost criminally incompetent technical “support” and you can see why I really hate them. When Pipex were good, they were great. When the connection worked I was (like 98% of the others) happy with their service – largely this was because I had no idea just how bad their customer support is, nor how bad they treat you when you have problem.<\/p>\n

I cant stress enough how much I would strongly recommend you did not use Pipex as an ISP<\/strong>.<\/p>\n

Share this:<\/h3>