bgpreport

Network · data from 2026-11-12

AS268647 DFLASH NET TELECOM E TURISMO

Registry name: AS268647 - DFLASH NET TELECOM E TURISMO LTDA, BR · PeeringDB

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

Announced routes

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

45.164.240.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
45.164.240.0/23 Valid Other IRR onlyTC 671 100% 67
45.164.242.0/23 Valid Other IRR onlyTC 671 100% 67
2804:5464::/32 Valid Other IRR onlyRADB, TC 633 100% 67
45.164.240.0/24 Valid Other IRR onlyTC 200 30% 54
45.164.241.0/24 Valid Other IRR onlyTC 11 2%low visibility 9
45.164.242.0/24 Valid Other IRR onlyTC 11 2%low visibility 9
45.164.243.0/24 Valid Other IRR onlyTC 11 2%low visibility 9

AS-SET

PeeringDB's irr_as_set for AS268647: AS-DFLASH. 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 (AS268647 isn't in the set, or no route object for AS268647 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 objectsAS268647 in itNot covered
AS-DFLASH TC 118 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 8 are in fix.csv.

  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
Route object: RIR45.164.240.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.164.240.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.164.242.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:5464::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR45.164.240.0/24Route object only in TC. Add it in the RIR database for the space.200 of 673
Route object: RIR45.164.241.0/24Route object only in TC. Add it in the RIR database for the space.11 of 673
Route object: RIR45.164.242.0/24Route object only in TC. Add it in the RIR database for the space.11 of 673
Route object: RIR45.164.243.0/24Route object only in TC. Add it in the RIR database for the space.11 of 673

Route objects not announced

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