bgpreport

Network · data from 2026-11-12

AS28821 UDST-QATAR University of Doha for Science and Technology

Registry name: UDST-QATAR University of Doha for Science and Technology, QA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28821, 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.

185.104.56.0/24 Valid Nonecovered by 185.104.56.0/22 673 100% 67
185.104.57.0/24 Valid Nonecovered by 185.104.56.0/22 673 100% 67
2a06:2f00::/48 Valid Nonecovered by 2a06:2f00::/29 635 100% 67
2a06:2f00:1::/48 Valid Nonecovered by 2a06:2f00::/29 635 100% 67
185.104.58.0/24 Valid Other IRR onlyRADB 672 100% 67
185.104.59.0/24 Valid Other IRR onlyRADB 672 100% 67

AS-SET

AS28821 isn't in PeeringDB, where networks name their 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 8 are in fix.csv.

  • Route object: none4
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none185.104.56.0/24No route object for it. A route object for 185.104.56.0/22 with origin AS28821 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28821 in the RIR database for the space.673 of 673
Route object: none185.104.57.0/24No route object for it. A route object for 185.104.56.0/22 with origin AS28821 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28821 in the RIR database for the space.673 of 673
Route object: none2a06:2f00::/48No route object for it. A route object for 2a06:2f00::/29 with origin AS28821 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28821 in the RIR database for the space.635 of 636
Route object: none2a06:2f00:1::/48No route object for it. A route object for 2a06:2f00::/29 with origin AS28821 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28821 in the RIR database for the space.635 of 636
Route object: RIR185.104.58.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR185.104.59.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

185.104.56.0/22RADB, RIPEValid
2a06:2f00::/29RIPEValid

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.