bgpreport

Network · data from 2026-11-12

AS207683 Jonas Emilsson

Registry name: jonasem Jonas Emilsson, SE · PeeringDB

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

Announced routes

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

2a0e:b107:330::/48 No ROA Nonecovered by 2a0e:b107:330::/44 635 100% 69
2a0e:b107:330::/44 No ROA RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS207683: AS207683:AS-JONASEM. 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 (AS207683 isn't in the set, or no route object for AS207683 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 objectsAS207683 in itNot covered
AS207683:AS-JONASEM RIPE 111 Yes 0

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

  • ROA: none2
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: none2a0e:b107:330::/48No ROA covers it. Add a ROA for AS207683, maxLength 48.635 of 636
Route object: none2a0e:b107:330::/48No route object for it. A route object for 2a0e:b107:330::/44 with origin AS207683 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207683 in the RIR database for the space.635 of 636
ROA: none2a0e:b107:330::/44No ROA covers it. Add a ROA for AS207683, maxLength 44.635 of 636

Route objects not announced

Every route object with origin AS207683 is announced.

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.