text: Title: Significant Response Delay After Idle Period in Version 3
  Body: ### Checklist
  
  - [X] I am sure the error is coming from aiogram code
  - [X] I have searched in the issue tracker for similar bug reports, including closed ones
  
  ### Operating system
  
  Oracle Linux 7
  
  ### Python version
  
  3.9
  
  ### aiogram version
  
  3.6.0
  
  ### Expected behavior
  
  The bot should respond promptly without significant delay, even after being idle.
  
  ### Current behavior
  
  The bot responds with a significant delay after being idle for more than 15 seconds.
  ![echo_bot](https://github.com/aiogram/aiogram/assets/59597538/a95bfa54-e8be-48dc-befc-9c1518ac6fb0)
  
  
  
  
  ### Steps to reproduce
  
  Deploy a standard bot on a server.
  Allow the bot to be idle for more than 15 seconds.
  Send a message to the bot.
  Observe the delay in the bot's response.
  
  ### Code example
  
  ```python3
  import os
  import sys
  import asyncio
  import logging
  
  from aiogram import Bot, types
  from aiogram import Dispatcher
  from aiogram.client.default import DefaultBotProperties
  from aiogram.enums import ParseMode
  
  TOKEN = os.getenv('TOKEN')
  
  logging.basicConfig(
      level=logging.INFO,
      format="%(asctime)s - %(levelname)s [%(name)s] - %(message)s",
      stream=sys.stdout,
      force=True,
  )
  logger = logging.getLogger(__name__)
  
  dp = Dispatcher()
  
  @dp.message()
  async def echo(message: types.Message):
      logger.info('Handler Start')
      await message.answer(message.text)
      logger.info('Handler End')
  
  
  async def main():
      bot = Bot(
          token=TOKEN, 
          default=DefaultBotProperties(parse_mode=ParseMode.HTML)
      )
      await dp.start_polling(bot, skip_updates=True)
  
  
  if __name__ == '__main__':
      try:
          logger.info("Starting bot")
          asyncio.run(main())
      except (KeyboardInterrupt, SystemExit):
          logger.info("Bot stopped!")
  ```
  
  
  ### Logs
  
  _No response_
  
  ### Additional information
  
  This issue is not present in version 2.x.