bgpreport

Network · data from 2026-11-12

AS53808 MoeDove Next Generation Network

Registry name: MOEDOVE-N2 - MoeDove, US · PeeringDB

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

Announced routes

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

64.204.91.0/24 Invalid: origin Other origin only 9 1%low visibility 8
44.30.121.0/24 No ROA Other IRR onlyRADB 671 100% 67
157.254.178.0/24 Valid Other IRR onlyRADB 671 100% 67
45.87.102.0/24 Valid Other IRR onlyRADB 670 100% 67
45.87.103.0/24 Valid Other IRR onlyRADB 670 100% 67
45.196.238.0/24 Valid Other IRR onlyRADB 669 99% 67
45.196.239.0/24 Valid Other IRR onlyRADB 668 99% 67
23.151.104.0/24 Valid RIR databaseALTDB, ARIN, RADB 671 100% 67
45.87.102.0/23 Valid RIR databaseRADB, RIPE 671 100% 67
147.79.1.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
216.238.52.0/24 Valid RIR databaseARIN 671 100% 68
216.238.53.0/24 Valid RIR databaseARIN 671 100% 68
23.175.24.0/24 Valid RIR databaseARIN 668 99% 67
2602:f92a:170::/48 Valid RIR databaseARIN 636 100% 67
2602:f92a:220::/48 Valid RIR databaseARIN 636 100% 67
2602:f92a:22a::/48 Valid RIR databaseARIN 636 100% 69
2602:f92a::/48 Valid RIR databaseARIN 635 100% 69
2602:f92a:222::/48 Valid RIR databaseARIN, RADB 635 100% 67
2602:f92a:100::/46 Valid RIR databaseARIN 634 100% 70
2602:f92a:230::/44 Valid RIR databaseARIN 634 100% 69
2602:f92a:314::/46 Valid RIR databaseARIN, RADB 634 100% 67
2602:f92a:230::/46 Valid RIR databaseARIN 94 15% 43
2602:f92a:100::/40 Valid RIR databaseARIN 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS53808: AS-MOEDOVE-N2. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS53808 isn't in the set, or no route object for AS53808 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS53808 in itNot covered
AS-MOEDOVE-N2 RADBlists itself further down1 member set in no database: AS199746:AS-NEXTSERV 85318819,803 Yes 1
ARIN (also)9 member sets in no database: AS139317:AS-ZXINC-ASIA, AS140915:AS-MKNT, AS153376:AS-DOWNSTREAM, AS198025:AS-DL-MD-DE, AS199310:AS-SELF … 4552,947 Yes 1

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 37 are in fix.csv.

  • ROA: origin1
  • ROA: none1
  • Route object: none1
  • Route object: RIR6
  • AS-SET: missing member1
  • Route object: not announced27
ChangePrefix or setDetailFull-table peers
ROA: origin64.204.91.0/24ROAs covering it name AS6079, not AS53808. If AS53808 should announce it, add a ROA for AS53808.9 of 673
Route object: none64.204.91.0/24Route objects for it name AS6079. Add a route object with origin AS53808 in the RIR database for the space.9 of 673
ROA: none44.30.121.0/24No ROA covers it. Add a ROA for AS53808, maxLength 24.671 of 673
Route object: RIR44.30.121.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR157.254.178.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.87.102.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.87.103.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR45.196.238.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR45.196.239.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
AS-SET: missing memberAS-MOEDOVE-N2AS-MOEDOVE-N2 (RADB) lists AS199746:AS-NEXTSERV; no IRR database read has it.

Route objects not announced

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

45.196.238.0/23RADBValid
157.254.178.0/23ARIN, RADBValid
168.222.25.0/24RADB, RIPEValid
188.255.216.0/24RADBValid
216.238.52.0/23ARINValid
2602:f92a::/32ARIN, RADBValid
2602:f92a::/36RADBValid
2602:f92a::/40ARINValid
2602:f92a::/44ARINValid
2602:f92a:124::/48ARINValid
2602:f92a:171::/48ARINValid
2602:f92a:200::/40ARINValid
2602:f92a:200::/48ARINValid
2602:f92a:220::/44ARINValid
2602:f92a:221::/48ARIN, RADBValid
2602:f92a:300::/40ARINValid
2602:f92a:300::/44ARINValid
2602:f92a:300::/48ARIN, RADBValid
2602:f92a:310::/44ARINValid
2602:f92a:310::/48ARIN, RADBValid
2602:f92a:800::/40ARINValid
2602:f92a:f100::/40ARINValid
2602:f92a:fe00::/39ARINValid
2602:f92a:fe00::/40ARINValid
2602:f92a:ff00::/40ARINValid
2602:f92a:ff00::/42ARINValid
2a0f:9400:6110::/48RIPEValid

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.