Not working mail.google.com, IP 10.0.0.1 and Rostelecom

Question

Google

Good day!

For the second or third time I observe a strange picture, which I cannot diagnose until it disappears.

When I try to go to mail.google.com, the browser says it can't connect.
If you call the ping command, it shows that the address 10.0.0.1 is being pinged and the pings pass, but the trace shows the normal Google IP address and also passes. Direct DNS queries return normal Google IPs. 8.8.8.8 and 8.8.4.4 are used as DNS.

/etc/hosts is clean both on the computer and on the Asus home router, and there are no warnings related to certificates either. The system is openSUSE, so the possibility of viruses is minimal. In addition, the version that this is the effect of the shamanism of Rostelecom itself is supported by the fact that they recently stopped issuing white IPs and began to drive clients into the gray network 10.0.0.0/8.

In this regard, I have two questions for the distinguished audience.
Please tell me if anyone else observes these effects when using Rostelecom or Rostelecom in Perm?
And how is it that both trace and dig see the correct IP, and the ping command writes that the address 10.0.0.1 is being pinged?

The problem occurs rarely and lasts a very short time, literally no more than 5-10 minutes.

update:
The city, as indicated above, is Perm, the provider is the former UralSvyazInform, aka Utel. So the observation of this problem is possible either in Perm or in the Urals.

Answer 1

ping mail.google.com 
PING googlemail.l.google.com (74.125.143.17) 56(84) bytes of data.

dig mail.google.com

;; ANSWER SECTION:
mail.google.com.        542243  IN      CNAME   googlemail.l.google.com.

As you can see, googlemail.l.google.com appears here - it would not hurt to indicate the result of dig for it ...

Answer 2

In Kamchatka, Rostelecom has the same song with Google mail.