Experienced same of recent. Found the reason here Tile Usage Policy.
OpenStreetMap data is free for everyone to use. Our tile servers are not.
Below are the minimum requirements that users of tile.openstreetmap.org must >adhere to. These may change in future, depending on available resources. >Should any users or patterns of usage nevertheless cause problems to the >service, access may still be blocked without prior notice. We will try to >contact relevant parties if possible, but cannot guarantee this.
But because OpenStreetMap data is free, many other organisations provide map >tiles made from OSM data. If your project doesn’t meet these requirements, >you can get OSM-derived map tiles elsewhere.
Requirements
Heavy use (e.g. distributing an app that uses tiles from >openstreetmap.org) is forbidden without prior permission from the System >Administrators. See below for alternatives.
Clearly display license attribution.
Do not actively or passively encourage copyright infringement.
Calls to /cgi-bin/export may only be triggered by direct end-user action. >(For example: “click here to export”.) The export call is an expensive >(CPU+RAM) function to run and will frequently reject when server is under >high load.
Highly Recommended: Do not hardcode any URL at tile.openstreetmap.org >into an app.
Recommended: add a link to https://www.openstreetmap.org/fixthemap to >allow your users to report and fix problems in our data.
Use other tile layers that uses osm to render map. Had to use this for map images to show on mobile
{tileLayer: "http://{s}.tile.opencyclemap.org/cycle/{z}/{x}/{y}.png",
zoomControl: false,
tileLayerOptions: {
opacity: 0.9,
detectRetina: true,
reuseTiles: true
},
scrollWheelZoom: false,
attributionControl: false
}
In a nutshell osm blocked the map tiles.