bgpreport

Network · data from 2026-11-12

AS269708 EMENET

Registry name: AS269708 - EMERSON PALMEIRA FIGUEIREDO-ME, BR · PeeringDB

7IPv4 routes 0.0% RPKI valid · 100.0% with a route object
3IPv6 routes 0.0% RPKI valid · 66.7% with a route object
0RPKI invalid 0 origin · 0 maxLength
10No 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 AS269708, seen from no peer

Announced routes

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

2804:68ac:8000::/34 No ROA Nonecovered by 2804:68ac::/32 356 56% 65
190.112.140.0/22 No ROA Other IRR onlyNTTCOM, RADB, TC 671 100% 67
190.112.140.0/23 No ROA Other IRR onlyRADB 671 100% 67
190.112.142.0/23 No ROA Other IRR onlyRADB 671 100% 67
2804:68ac::/32 No ROA Other IRR onlyNTTCOM, RADB, TC 635 100% 67
2804:68ac:4000::/34 No ROA Other IRR onlyRADB 356 56% 65
190.112.140.0/24 No ROA Other IRR onlyRADB 211 31% 56
190.112.141.0/24 No ROA Other IRR onlyRADB 211 31% 56
190.112.142.0/24 No ROA Other IRR onlyRADB 208 31% 56
190.112.143.0/24 No ROA Other IRR onlyRADB 208 31% 56

AS-SET

PeeringDB's irr_as_set for AS269708: AS269708. 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 (AS269708 isn't in the set, or no route object for AS269708 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 objectsAS269708 in itNot covered
AS269708 A single AS number, not a set: AS269708 (this network), 9 route objects.

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

  • ROA: none10
  • Route object: none1
  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
ROA: none2804:68ac:8000::/34No ROA covers it. Add a ROA for AS269708, maxLength 34.356 of 636
Route object: none2804:68ac:8000::/34No route object for it. A route object for 2804:68ac::/32 with origin AS269708 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269708 in the RIR database for the space.356 of 636
ROA: none190.112.140.0/22No ROA covers it. Add a ROA for AS269708, maxLength 22.671 of 673
Route object: RIR190.112.140.0/22Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none190.112.140.0/23No ROA covers it. Add a ROA for AS269708, maxLength 23.671 of 673
Route object: RIR190.112.140.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none190.112.142.0/23No ROA covers it. Add a ROA for AS269708, maxLength 23.671 of 673
Route object: RIR190.112.142.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:68ac::/32No ROA covers it. Add a ROA for AS269708, maxLength 32.635 of 636
Route object: RIR2804:68ac::/32Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:68ac:4000::/34No ROA covers it. Add a ROA for AS269708, maxLength 34.356 of 636
Route object: RIR2804:68ac:4000::/34Route object only in RADB. Add it in the RIR database for the space.356 of 636
ROA: none190.112.140.0/24No ROA covers it. Add a ROA for AS269708, maxLength 24.211 of 673
Route object: RIR190.112.140.0/24Route object only in RADB. Add it in the RIR database for the space.211 of 673
ROA: none190.112.141.0/24No ROA covers it. Add a ROA for AS269708, maxLength 24.211 of 673
Route object: RIR190.112.141.0/24Route object only in RADB. Add it in the RIR database for the space.211 of 673
ROA: none190.112.142.0/24No ROA covers it. Add a ROA for AS269708, maxLength 24.208 of 673
Route object: RIR190.112.142.0/24Route object only in RADB. Add it in the RIR database for the space.208 of 673
ROA: none190.112.143.0/24No ROA covers it. Add a ROA for AS269708, maxLength 24.208 of 673
Route object: RIR190.112.143.0/24Route object only in RADB. Add it in the RIR database for the space.208 of 673

Route objects not announced

Every route object with origin AS269708 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.