TLDR: Tho highly rated as a 5 star airline, Singapore Airlines booking process with their own subsidiary is braindead.

--

I wanted to book a code share flight from MDC to SIN to HAN. While it is a codeshare flight between two different airlines, Scoot, the airline that provides the first segment, is a wholly owned subsidiary of Singapore Airlines.

I needed to purchase an extra 10 kg of baggage. There is nowhere that I get to see the extra baggage fees when I'm booking the flight. I contacted customer support and they said I had to book the flight before I could add the extra baggage. I stated that that seems insane because you can't tell me the price of the extra baggage before I book a nonrefundable flight. Well that's the rule so I had to suck it up. 

I booked the flight and then per the instructions I was given, I go back to manage my booking on Singapore Airlines website. 

You can't book the extra luggage online.
Contact support. Ugh. 

I contact support via their chat session on the website. The agent spends 40 MINUTES trying to book the extra 10 kg of luggage and it's going to cost $119. Oh well, fine. But she is unable to process it because of system errors. 

She said she needs to call me and we will use the automated system online so I can enter my credit card payment. 

I enter the payment with her, and almost 1 hour later I am finished with a process that should have taken 30 seconds. 

As a bonus when I initially tried to book this through Scoot rather than Singapore Airlines, my outbound flight from MDC doesn't even show available on Scoot’s website! And after booking with Singapore Airlines where I received two different booking references, one for each segment, neither booking references is recognized by Scoot's website. I assume that this is due to (an unacceptable) system integration delay and in a few hours hopefully it will be there so I can pick my seat for the first segment. 

What a customer hostile process!

I know these are the general frustrations people have with codeshare flights, but given the fact that Singapore Airlines own Scoot you would think it would be a little more frictionless. 

And in general, with code share flights, shouldn't it be the responsibility of the airline that is marketing and selling and presumably profiting extra to make sure that the customer’s end-to-end experience is painless and ready?

Hi all!

I'm hoping to travel from Bangkok to Dan Sai for the Phi Ta Khon Ghost Mask Festival next weekend.

I am realizing that I am late in my planning as accomodations in the area are unavailable, even 30 minutes away bu car in Phu Ruea.

If I fly in to Loei, there are plenty of options there, but that would be a 2-3 hour round trip drive to Dan Sai each day.

Any recommendations?

I sent CS Support a ticket complaining about how I'm getting stay requests even though my previous status was "Can't Host". It took them 11 DAYS to respond with this moronic explanation

--- begin CS Support response ---

Thanks for letting us know. These are valid concerns, and you're not alone in raising them.

A few things worth knowing: last login and "Accepting Guests" status haven't disappeared entirely; they work differently now. Search automatically ranks active hosts higher, so inactive profiles drop down without you needing to filter. And instead of a manual hosting status, hosts step out of search results automatically when they decline a request. The full details on what changed and why are in the help article linked below

--- end CS Support response ---

My reply:

That's a terrible design decision.

1. If I'm actively hosting, I might have a valid reason for declining a request and the next person to ask might be accepted, so why would you filter an active host out of search results because they declined once?

2. If I'm NOT hosting, as reported, you are wasting my time AND the potential guest's time

For you to claim how this is such an improvement over letting members manage their own hosting status shows a clear lack of understanding of how we (used to) use the platform.

Why not just be honest with the user base and say you are deprioritizing the hospitality exchange (the core feature...) aspect of the platform. It's clear to all of us that this is what's happening.

Also, to take 11 days to reply to a support request is unacceptable.

Rant over. 😏

I was diving on a liveaboard in the Philippines at Tubbataha Reef this week (June 2026). I was using nitrox all week and except for the first dive when the air mix was 31% oxygen, the whole rest of the week was 30%

We did 20 dives this week. On the 18th dive today, I had a strange thing happen. Every time I would get to 25m deep, my PO2 alarm would go off like crazy until I ascended a few meters. I just shallowed up the dive for the rest of the dive as our group was diving pretty conservatively anyway (we had 3 divers on air vs the rest of us on nitrox)

I talked to a few of the guys in the group about what was happening. They thought, like I did, that there must be a sensor issue with my Genesis Centauri dive computer (sand blockage or calibration issue or hardware failure)

I thought I would try again on the next dive. Same issue - right at 25m the PO2 alarm goes off. shallowed up, finished the dive. 

I was resigned to get the computer serviced when I got to Bangkok next week.

Later at dinner, I was showing the computer to some of the other guys in the group who were looking to upgrade but at a modest price. I was showing them how easy it is to set values vs other basic computers like the Zoop. I happened to be on the nitrox settings screen and was surprised to see it was set at 40% not 30%! I absolutely did not knowingly change this value, but that explains what was happening - MOD* for 40% nitrox is 25m. Mystery solved. Works as designed.  User error.

I have almost 550 dives but this was still a good learning experience for me. Check, double check, triple check,.

* Maximum Operating Depth - It is the deepest safe depth for a specific nitrox mix before the partial pressure of oxygen (PO2) hits dangerous levels and risks causing oxygen toxicity