bgpreport

Network · data from 2026-11-12

AS272559 JAPANET TELECOM

Registry name: AS272559 - ULISSES DE OLIVEIRA SANTOS - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272559, 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:8520::/35 Valid Nonecovered by 2804:8520::/34 351 55% 64
2804:8520:120::/44 Valid Nonecovered by 2804:8520::/34 351 55% 64
2804:8520:f70::/44 Valid Nonecovered by 2804:8520::/34 351 55% 64
2804:8520:f80::/41 Valid Nonecovered by 2804:8520::/34 351 55% 64
2804:8520:f80::/42 Valid Nonecovered by 2804:8520::/34 351 55% 64
2804:8520:f80::/43 Valid Nonecovered by 2804:8520::/34 351 55% 64
2804:8520:fa0::/43 Valid Nonecovered by 2804:8520::/34 351 55% 64
2804:8520:fc0::/42 Valid Nonecovered by 2804:8520::/34 351 55% 64
2804:8520:fc0::/43 Valid Nonecovered by 2804:8520::/34 351 55% 64
2804:8520:fe0::/43 Valid Nonecovered by 2804:8520::/34 351 55% 64
2804:8520:2000::/35 Valid Nonecovered by 2804:8520::/34 351 55% 64
2804:8520:4000::/35 Valid Nonecovered by 2804:8520:4000::/34 351 55% 64
2804:8520:6000::/35 Valid Nonecovered by 2804:8520:4000::/34 351 55% 64
2804:8520:8000::/35 Valid Nonecovered by 2804:8520:8000::/34 351 55% 64
2804:8520:a000::/35 Valid Nonecovered by 2804:8520:8000::/34 351 55% 64
2804:8520:c000::/35 Valid Nonecovered by 2804:8520:c000::/34 351 55% 64
2804:8520:e000::/35 Valid Nonecovered by 2804:8520:c000::/34 351 55% 64
2804:8520::/32 Valid Other IRR onlyRADB, TC 634 100% 67
2804:8520::/33 Valid Other IRR onlyRADB, TC 351 55% 64
2804:8520::/34 Valid Other IRR onlyTC 351 55% 64
2804:8520:4000::/34 Valid Other IRR onlyTC 351 55% 64
2804:8520:8000::/33 Valid Other IRR onlyRADB, TC 351 55% 64
2804:8520:8000::/34 Valid Other IRR onlyTC 351 55% 64
2804:8520:c000::/34 Valid Other IRR onlyTC 351 55% 64

AS-SET

PeeringDB's irr_as_set for AS272559: AS272559:AS-ALL. 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 (AS272559 isn't in the set, or no route object for AS272559 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 objectsAS272559 in itNot covered
AS272559:AS-ALL TC 2210 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 24 are in fix.csv.

  • Route object: none17
  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
Route object: none2804:8520::/35No route object for it. A route object for 2804:8520::/34 with origin AS272559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272559 in the RIR database for the space.351 of 636
Route object: none2804:8520:120::/44No route object for it. A route object for 2804:8520::/34 with origin AS272559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272559 in the RIR database for the space.351 of 636
Route object: none2804:8520:f70::/44No route object for it. A route object for 2804:8520::/34 with origin AS272559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272559 in the RIR database for the space.351 of 636
Route object: none2804:8520:f80::/41No route object for it. A route object for 2804:8520::/34 with origin AS272559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272559 in the RIR database for the space.351 of 636
Route object: none2804:8520:f80::/42No route object for it. A route object for 2804:8520::/34 with origin AS272559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272559 in the RIR database for the space.351 of 636
Route object: none2804:8520:f80::/43No route object for it. A route object for 2804:8520::/34 with origin AS272559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272559 in the RIR database for the space.351 of 636
Route object: none2804:8520:fa0::/43No route object for it. A route object for 2804:8520::/34 with origin AS272559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272559 in the RIR database for the space.351 of 636
Route object: none2804:8520:fc0::/42No route object for it. A route object for 2804:8520::/34 with origin AS272559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272559 in the RIR database for the space.351 of 636
Route object: none2804:8520:fc0::/43No route object for it. A route object for 2804:8520::/34 with origin AS272559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272559 in the RIR database for the space.351 of 636
Route object: none2804:8520:fe0::/43No route object for it. A route object for 2804:8520::/34 with origin AS272559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272559 in the RIR database for the space.351 of 636
Route object: none2804:8520:2000::/35No route object for it. A route object for 2804:8520::/34 with origin AS272559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272559 in the RIR database for the space.351 of 636
Route object: none2804:8520:4000::/35No route object for it. A route object for 2804:8520:4000::/34 with origin AS272559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272559 in the RIR database for the space.351 of 636
Route object: none2804:8520:6000::/35No route object for it. A route object for 2804:8520:4000::/34 with origin AS272559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272559 in the RIR database for the space.351 of 636
Route object: none2804:8520:8000::/35No route object for it. A route object for 2804:8520:8000::/34 with origin AS272559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272559 in the RIR database for the space.351 of 636
Route object: none2804:8520:a000::/35No route object for it. A route object for 2804:8520:8000::/34 with origin AS272559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272559 in the RIR database for the space.351 of 636
Route object: none2804:8520:c000::/35No route object for it. A route object for 2804:8520:c000::/34 with origin AS272559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272559 in the RIR database for the space.351 of 636
Route object: none2804:8520:e000::/35No route object for it. A route object for 2804:8520:c000::/34 with origin AS272559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272559 in the RIR database for the space.351 of 636
Route object: RIR2804:8520::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:8520::/33Route object only in RADB, TC. Add it in the RIR database for the space.351 of 636
Route object: RIR2804:8520::/34Route object only in TC. Add it in the RIR database for the space.351 of 636
Route object: RIR2804:8520:4000::/34Route object only in TC. Add it in the RIR database for the space.351 of 636
Route object: RIR2804:8520:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.351 of 636
Route object: RIR2804:8520:8000::/34Route object only in TC. Add it in the RIR database for the space.351 of 636
Route object: RIR2804:8520:c000::/34Route object only in TC. Add it in the RIR database for the space.351 of 636

Route objects not announced

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