As noted above, there's a good chance it will actually validate married bucket availability when you go to purchase and it will bomb out at that point when it discovers there is no actual bucket availability in S on the married segments. The fare search engines employ caching to make their searches go faster, so there's also the possibility it's using stale cache information. Again, once you go to purchase it has to validate the true availability and will tell you the fare is no long available.