bgpreport

Network · data from 2026-11-12

AS49585 CoreRoute UG (haftungsbeschränkt)

Registry name: COREROUTE-AS CoreRoute UG (haftungsbeschraenkt), DE · PeeringDB

6IPv4 routes 83.3% RPKI valid · 83.3% with a route object
10IPv6 routes 90.0% RPKI valid · 80.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
1No ROA 3 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS49585, seen from no peer

Announced routes

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

2a07:59c6:e000::/48 Invalid: origin None 1 0%low visibility 1
44.31.89.0/24 No ROA Other IRR onlyRADB 670 100% 68
2602:faaf:4::/48 Valid Nonecovered by 2602:faaf::/40 635 100% 69
104.156.139.0/24 Valid None 3 0%low visibility 3
23.146.24.0/24 Valid RIR databaseALTDB, ARIN, RADB 671 100% 68
104.156.136.0/24 Valid RIR databaseARIN 671 100% 68
104.156.137.0/24 Valid RIR databaseARIN 671 100% 68
104.156.138.0/24 Valid RIR databaseARIN 671 100% 68
2602:faaf:1::/48 Valid RIR databaseALTDB, ARIN, RADB 635 100% 69
2602:faaf:2::/48 Valid RIR databaseALTDB, ARIN, RADB 635 100% 69
2602:faaf:5::/48 Valid RIR databaseARIN 635 100% 69
2602:faaf:6::/48 Valid RIR databaseARIN 635 100% 69
2602:faaf:8::/48 Valid RIR databaseARIN 635 100% 69
2602:faaf:10::/48 Valid RIR databaseARIN 635 100% 69
2a11:ca80::/40 Valid RIR databaseRIPE 632 99% 69
2a11:ca80:100::/40 Valid RIR databaseRIPE 632 99% 69

AS-SET

PeeringDB's irr_as_set for AS49585: AS-COREROUTE. 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 (AS49585 isn't in the set, or no route object for AS49585 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 objectsAS49585 in itNot covered
AS-COREROUTE RIPE 12961,025 Yes 2

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

  • ROA: origin1
  • ROA: none1
  • Route object: none3
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: origin2a07:59c6:e000::/48ROAs covering it name AS44652, not AS49585. If AS49585 should announce it, add a ROA for AS49585.1 of 636
Route object: none2a07:59c6:e000::/48No route object for it. Add a route object with origin AS49585 in the RIR database for the space.1 of 636
ROA: none44.31.89.0/24No ROA covers it. Add a ROA for AS49585, maxLength 24.670 of 673
Route object: RIR44.31.89.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: none2602:faaf:4::/48No route object for it. A route object for 2602:faaf::/40 with origin AS49585 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49585 in the RIR database for the space.635 of 636
Route object: none104.156.139.0/24No route object for it. Add a route object with origin AS49585 in the RIR database for the space.3 of 673

Route objects not announced

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

23.149.40.0/24ARINValid
149.245.222.0/24RIPEValid
2001:470:2a7::/48ARINInvalid: origin
2602:faaf::/40ARINNo ROA
2602:fafd:901::/48ARINNo ROA

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.