bgpreport

Network · data from 2026-11-12

AS29039 ECHOTEL-UG

Registry name: ECHOTEL-UG - IDDQD-AS, UG · PeeringDB

16IPv4 routes 93.8% RPKI valid · 93.8% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 1 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS29039, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS29039, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
216.104.194.0/23 No ROA Other IRR onlyRADB 10 1%low visibility 6
216.104.199.0/24 Valid Nonecovered by 216.104.196.0/22 673 100% 67
216.104.200.0/24 Valid Other IRR onlyRIPE-NONAUTH 671 100% 68
216.104.201.0/24 Valid Other IRR onlyRADB, RIPE-NONAUTH 671 100% 68
216.104.204.0/24 Valid Other IRR onlyRADB, RIPE-NONAUTH 671 100% 68
216.104.205.0/24 Valid Other IRR onlyRADB, RIPE-NONAUTH 671 100% 68
216.104.206.0/24 Valid Other IRR onlyRADB, RIPE-NONAUTH 671 100% 68
216.104.207.0/24 Valid Other IRR onlyRADB, RIPE-NONAUTH 671 100% 68
216.104.193.0/24 Valid RIR databaseARIN, RADB 671 100% 68
216.104.194.0/24 Valid RIR databaseARIN, RADB 671 100% 68
216.104.195.0/24 Valid RIR databaseARIN 671 100% 68
216.104.196.0/24 Valid RIR databaseARIN, RADB 671 100% 68
216.104.197.0/24 Valid RIR databaseARIN 671 100% 68
216.104.198.0/24 Valid RIR databaseARIN 671 100% 68
216.104.202.0/24 Valid RIR databaseARIN, RADB, RIPE-NONAUTH 671 100% 68
216.104.196.0/22 Valid RIR databaseARIN, RADB 2 0%low visibility 2

AS-SET

AS29039's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 17 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: RIR7
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none216.104.194.0/23No ROA covers it. Add a ROA for AS29039, maxLength 23.10 of 673
Route object: RIR216.104.194.0/23Route object only in RADB. Add it in the RIR database for the space.10 of 673
Route object: none216.104.199.0/24No route object for it. A route object for 216.104.196.0/22 with origin AS29039 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29039 in the RIR database for the space.673 of 673
Route object: RIR216.104.200.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
Route object: RIR216.104.201.0/24Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
Route object: RIR216.104.204.0/24Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
Route object: RIR216.104.205.0/24Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
Route object: RIR216.104.206.0/24Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
Route object: RIR216.104.207.0/24Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673

Route objects not announced

Route objects with origin AS29039 whose prefix no peer sees AS29039 announce. Many are kept on purpose (backup routes, space announced only in some places).

41.138.192.0/20RADBNo ROA
216.104.196.0/23RADBValid
216.104.200.0/21RIPE-NONAUTHNo ROA
216.104.200.0/22RIPE-NONAUTHNo ROA
216.104.200.0/23ARIN, RIPE-NONAUTHValid
216.104.202.0/23RIPE-NONAUTHNo ROA
216.104.204.0/23ARINValid
216.104.206.0/23ARIN, RIPE-NONAUTHValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.